Smarter Device Manager¶
Manage hardware resource allocation without a need for privileged containers.
This chart is not maintained by the upstream project and any issues with the chart should be raised here
Installing the Chart¶
To install the chart with the release name
Uninstalling the Chart¶
To uninstall the
The command removes all the Kubernetes components associated with the chart including persistent volumes and deletes the release.
Specify each parameter using the
--set key=value[,key=value] argument to
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart.
Please consider overriding the default configuration through
values.yaml. For example:
The above configuration allows up to twenty pods to make use of
/dev/rtc0 and each of
/dev/video[0-9]* devices. Only one pod at a time can use any of the discovered host
/dev/ttyACM[0-9]* devices. This means that if a pod has reserved a dongle at
/dev/ttyACM0, another pod requesting the same device will stay pending.
Once the devices are discovered, they will be added as allocatable resources to the nodes:
The hardware is requested by pods through
In this case host device
/dev/ttyUSB-Conbee-2 will be given at the same path, and the pod will only be created when this device is available.
Important: When deploying an application Helm chart you can add more values from the bjw-s common library chart here
|config||string||See values.yaml||Override default configuration [ref]|
|hostNetwork||bool|| ||When using hostNetwork make sure you set dnsPolicy to |
|image.pullPolicy||string|| ||image pull policy|
|image.repository||string|| ||image repository|
|image.tag||string|| ||image tag|
|persistence||object||See values.yaml||Configure persistence settings for the chart under this key.|
|priorityClassName||string|| ||Custom priority class for different treatment by the scheduler Setting this is not necessary, but it is recommended. [ref]|
|securityContext||object||See values.yaml||Configure the securityContext for this pod [ref]|
|termination.messagePath||string|| ||Configure the path at which the file to which the main container's termination message will be written. Overrides the default of |
|termination.messagePolicy||string|| ||Indicate how the main container's termination message should be populated. Valid options are |
Autogenerated from chart metadata using helm-docs