charts/charts/stable/zigbee2mqtt/README_CONFIG.md.gotmpl
Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs 6b9dbce1d1
[zigbee2mqtt] Migrate to common v3 (#956)
* added privileged flag to readme for clarity (#955)

* [zigbee2mqtt] Upgrade to common v3

Signed-off-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <me@bjw-s.dev>

* Small README fix

Signed-off-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <me@bjw-s.dev>

Co-authored-by: itobey <itobey@users.noreply.github.com>
2021-06-09 14:02:15 -04:00

46 lines
1.2 KiB
Go Template

{{- 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`
If you are getting errors, that the device cannot be opened when starting Zigbee2Mqtt, try uncommenting the privileged flag:
```
securityContext:
privileged: true
```
{{- end -}}