Note: See the cluster setup steps for information on how to set the crictl configuration variableAKRI_HELM_CRICTL_CONFIGURATION
kubectl get akrii
. Note akrii
is a short name for Akri Instance. All the instances will be named in the format <configuration-name>-<id>
, where id
varies whether or not the device is sharable or visible by multiple nodes.id
is a hash of a descriptor of the device and the name of the node that can see the device. For example, the id
of an Instance representing a usb camera at devnode /dev/video0
on a node named workerA would be hash(/dev/video0workerA)
.id
is only a hash of the descriptor of the device. This way, all agents create or modify an Instance with the same name for the same device. For example, since IP cameras are sharable, the id
for an IP camera would be hash(uri)
.onvif-camera
by adding --set onvif.configuration.name=onvif-camera
to your installation command. Now, you can schedule pods that request these Instances as resources. Assuming the Configuration name has been set to onvif-camera
, you can request the onvif-camera-<id>
Instance as a resource by adding the following to the PodSpec of your Deployment or Job: