The module does not require any configuration (it works right out-of-the-box).
The module is enabled by default in the following bundles: Default
, Managed
.
The module is disabled by default in the Minimal
bundle.
The module is configured using the ModuleConfig custom resource named pod-reloader
(learn more about setting up Deckhouse…).
Example of the ModuleConfig/pod-reloader
resource for configuring the module:
apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
name: pod-reloader
spec:
version: 1
enabled: true
settings: # <-- Module parameters from the "Parameters" section below.
Parameters
Schema version: 1
- nodeSelector
The same as in the pods’
spec.nodeSelector
parameter in Kubernetes.If the parameter is omitted or
false
, it will be determined automatically.Example:
nodeSelector: disktype: ssd
- reloadOnCreate
Rollout the workload in case of creating a ConfigMap or Secret.
Enabling the parameter will cause the workload to restart not only when changing the corresponding ConfigMap or Secret, but also when creating it.
Default:
true
Examples:
reloadOnCreate: true
reloadOnCreate: false
- tolerations
The same as in the pods’
spec.tolerations
parameter in Kubernetes;If the parameter is omitted or
false
, it will be determined automatically.Example:
tolerations: - key: key1 operator: Equal value: value1 effect: NoSchedule - key: key1 operator: Exists effect: NoSchedule
- tolerations.effect
- tolerations.key
- tolerations.operator
- tolerations.tolerationSeconds
- tolerations.value