2021-02-17 22:43:56 +00:00
|
|
|
{{- define "custom.custom.configuration.header" -}}
|
|
|
|
## Custom configuration
|
|
|
|
{{- end -}}
|
|
|
|
|
|
|
|
{{- define "custom.custom.configuration" -}}
|
|
|
|
{{ template "custom.custom.configuration.header" . }}
|
|
|
|
|
|
|
|
**IMPORTANT NOTE:** a zigbee controller device must be accessible on the node where this pod runs, in order for this chart to function properly.
|
|
|
|
|
|
|
|
First, you will need to mount your zigbee device into the pod, you can do so by adding the following to your values:
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
additionalVolumeMounts:
|
|
|
|
- name: usb
|
|
|
|
mountPath: /path/to/device
|
|
|
|
|
|
|
|
additionalVolumes:
|
|
|
|
- name: usb
|
|
|
|
hostPath:
|
|
|
|
path: /path/to/device
|
|
|
|
```
|
|
|
|
|
|
|
|
Second you will need to set a nodeAffinity rule, for example:
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
affinity:
|
|
|
|
nodeAffinity:
|
|
|
|
requiredDuringSchedulingIgnoredDuringExecution:
|
|
|
|
nodeSelectorTerms:
|
|
|
|
- matchExpressions:
|
|
|
|
- key: app
|
|
|
|
operator: In
|
|
|
|
values:
|
|
|
|
- zigbee-controller
|
|
|
|
```
|
|
|
|
|
|
|
|
... where a node with an attached zigbee controller USB device is labeled with `app: zigbee-controller`
|
2021-06-09 18:02:15 +00:00
|
|
|
|
|
|
|
If you are getting errors, that the device cannot be opened when starting Zigbee2Mqtt, try uncommenting the privileged flag:
|
|
|
|
|
|
|
|
```
|
|
|
|
securityContext:
|
|
|
|
privileged: true
|
|
|
|
```
|
2021-02-17 22:43:56 +00:00
|
|
|
{{- end -}}
|