akri-onvif-video-broker), which acts as a frame server.
akri-onvif-video-brokerin the figure.
akri-onvif-video-brokerpods, which were specified in the Configuration. The Controller also creates a Kubernetes service for each ONVIF camera along with one service for all the ONVIF cameras.
agent.full=true. By default, a slim Agent without any embedded Discovery Handlers is deployed and the required Discovery Handlers can be deployed as DaemonSets. This documentation will use that strategy, deploying ONVIF Discovery Handlers by specifying
onvif.discovery.enabled=truewhen installing Akri.
helm inspect values akri-helm-charts/akri). More information about the Akri Helm charts can be found in the user guide. To apply the ONVIF Configuration to your cluster, simply set
onvif.configuration.enabled=truealong with any of the following additional Configuration settings when installing Akri.
onvif.configuration.capacitysetting to reflect the correct number. For example, if your high availability needs are met by having 1 redundant pod, you can update the Configuration like this by setting
capacitydefaults to one. The brokers will supply the automatically created Instance Services and the Configuration Service with frames.
discoveryTimeoutSecondsfor IP cameras. This timeout can be increased or decreased as desired, and defaults to 1 second if not configured. It can be set in the Configuration like this: