Verifying Milestone AI Bridge is running (Kubernetes)
After deploying the Milestone AI Bridge, you can verify all pods are running as expected by opening a terminal and running the following command
kubectl get pods -n aibridge
If you have created your own namespace, replace the aibridge namespace with your namespace after the -n parameter.
The output of the command will resemble the example below.
Your installation may contain additional pods running in your cluster, but the ones displayed below should be listed.
| POD | READY | STATUS | RESTARTS | AGE |
|---|---|---|---|---|
| aib-aibridge-broker-ccc86479-676mc | 1/1 | Running | 0 | 13m |
| aib-aibridge-connector-8c5b9dbf7-jdjcd | 1/1 | Running | 0 | 13m |
| aib-aibridge-fuseki-dbb789678-s5nv5 | 1/1 | Running | 0 | 13m |
| aib-aibridge-health-58bf7fbcb7-4c8xj | 1/1 | Running | 0 | 13m |
| aib-aibridge-kafka-broker-77cd764b4f-fh4ms | 1/1 | Running | 0 | 13m |
| aib-aibridge-proxy-7bd9d9d59-9hpdj | 1/1 | Running | 0 | 13m |
| aib-aibridge-streaming-8d75885d9-qqf9c | 1/1 | Running | 0 | 13m |
| aib-aibridge-webservice-564d7dbc68-cwfrv | 1/1 | Running | 0 | 13m |
If you see aibridge-init-xxxxx pod in the list with the status of Running, the Milestone AI Bridge is still initializing and not ready for operations.
If the aibridge-init-xxxxx pod does not complete within a couple of minutes, you can check the log file of the pod by opening a terminal and running the following command:
kubectl logs aib-aibridge-init-<xxxxx> -n aibridge
where <xxxxx> in the pod name will be different for every deployment.