helm inspect values akri-helm-charts/akri). For more advanced Configuration changes that are not aided by our Helm chart, we suggest creating a Configuration file using Helm and then manually modifying it.
udev.configuration.enabledand add a udev rule. For OPC UA, substitute with
brokerPodSpecproperty is a full PodSpec and can be modified as such. For example, to allow the master Node to have a protocol broker Pod scheduled to it, modify the Configuration, ONVIF in this case, like so:
brokerJobSpecproperty is a full JobSpec and can be modified as such. Akri's Helm chart enables modifying the
backoffLimitfields of the JobSpec. Other fields of the JobSpec and the PodSpec within the JobSpec can be specified in a similar manner as described in the modifying the PodSpec section.
configurationServiceSpecproperties are full ServiceSpecs and can be modified as such. The simplest reason to modify either might be to specify different ports (perhaps 8085 and 8086):
akri-udevConfiguration have been created by running:
helm upgradecommand. It upgrades an existing release according to the values provided, only updating what has changed. Simply modify your
helm installcommand to reflect the new desired state of Akri and replace
helm upgrade. Using the ONVIF protocol implementation as an example, say an IP camera with IP address 10.0.0.1 is malfunctioning and should be filtered out of discovery, the following command could be run:
helm upgrade --set onvif.configuration.discoveryDetails.ipAddresses.items=10.0.0.1; rather, it includes all the old settings along with the new one. Also, note that we assumed you specified a broker pod image in your original installation command, so that brokers were deployed to utilize discovered cameras.
helm upgradeor via a new Helm installation.
helm upgrade. For example, if you originally installed just the ONVIF Configuration and now also want to discover local cameras via udev, as well, simply run the following:
brokerSpecof the Configuration using one of the strategies from the section on modifying a deployed Configuration.
Note: The Agent and Controller can only gracefully handle changes to the
brokerSpec. If any other parts of the Configuration are modified, the Agent will restart discovery, deleting and recreating the Instances.
helm delete, or kubectl.
helm upgrade. For example, if both ONVIF and udev Configurations have been installed in a cluster, the udev Configuration can be deleted by only specifying the ONVIF Configuration in a
helm upgradecommand like the following:
udev-configin this example), the Configuration can be deleted by deleting the installation.
kubectl get akric. If both udev and ONVIF Configurations have been applied with capacities of 5. The output should look like the following:
agent.full=true, like so:
<discovery handler name>.discovery.enabled=truewhen installing Akri. For example, Akri is installed with the OPC UA and ONVIF Discovery Handlers like so: