akri-onvif-video-broker
), which acts as a frame server.akri-onvif-video-broker
in the figure.akri-onvif-video-broker
pods, 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=true
when 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=true
along with any of the following additional Configuration settings when installing Akri.brokerPod
) in the Configuration. Alternatively, if it meets your scenario, you could use the Akri frame server broker ("ghcr.io/project-akri/akri/onvif-video-broker"). If you would rather manually deploy pods to utilize the cameras advertized by Akri, don't specify a broker pod and see our documentation on requesting resources advertized by Akri.Note only abrokerJob
ORbrokerPod
should be specified.
brokerJob
) in the Configuration. A Kubernetes Job deploys a set number of terminating Pods.Note only abrokerJob
ORbrokerPod
should be specified.
OnFailure
RestartPolicy
for the Job. Can either be OnFailure
or Never
for Jobs.onvif.configuration.capacity
setting 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 onvif.configuration.capacity=2
.Note: See the cluster setup steps for information on how to set the crictl configuration variableAKRI_HELM_CRICTL_CONFIGURATION
capacity
defaults to one. The brokers will supply the automatically created Instance Services and the Configuration Service with frames.discoveryTimeoutSeconds
for 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: