Kubernetes AI Bridge not receiving or displaying metadata. (Bounding Boxes)

General
1

Hi! I recently deployed a version of the AI bridge starting with docker. I was able to get it working and to show live metadata (bounding boxes). But with the Kubernetes version I have not been able to successfully show metadata. I have troubleshooted all the areas I can think of. The bridge says its connected, I have a camera subscribed to the metadata channel, the IVA app is successfully connected. The protocol for transportation is MQTT. All logs show the MQTT packets come in, the app transposes them to onvif analytics format (XML) sends to the AI bridge and successfully returns a 200 from the Bridge. No IVA app code has changed when it was working with Docker AI bridge.

The app successfully registers with graphql, I have queried and confirmed everything is working as it should.

I was originally on AI Bridge 2.0.4, I even rolled it back to 2.0.3 to see if it would work.

All Pods are in healthy order. But when I check logs on connector, or streaming - while running a live test, I see no output. Which tells me the metadata isn’t reaching the pipeline.

I will say I’m pretty new to running Kubernetes and maybe I’m missing something. I have also learned that if Kafka topic offsets don’t increase, its also a sign of no metadata entering Kafka.

Hope to hear back soon and can get this resolved. Here is a little snippet of app registering successfully -

image
image1893×518 41.7 KB

image
image847×664 84.1 KB

3

Did you update the VPS Driver settings accordingly to your environment change?

Please check the logs for VPS Driver oddities, typically located here:

‪C:\ProgramData\Milestone\XProtect Recording Server\Logs\DeviceHandling.log

The VPS Driver settings are used on the Recording Server to reach to the AI Bridge, so in your settings, like:

image
image1227×296 10 KB

the url after “VPSNODES,” must be reachable from the Recording Server, and of course valid for the environment.

It could be an idea to unsubscribe form the metadata stream topic, and then resubscribe (= setting up a new VPS Driver with correct settings).

4

Thanks I’ll look into this. On a side note, when using Kubernetes, is it mandatory to secure it? Even if both endpoints are in a internal network?

Since our systems are all internal, I have not secured Kubernetes AI bridge or the VMS

5

Thanks for that Breadcrumb! analyzing that log, my output was:

VpsThread - VpsThread - Error: Unable to connect to the remote server

This led me to test connections from the management client server to the AI bridge. I started getting unauthorized replies. Going through a few other possibilities, I found out I was missing DNS Mapping in the CoreDNS k8s. Once the hosts was mapped, it started receiving in metadata.

Thanks again!