You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the helm charts don't roll the corresponding pods for a given statefulset when an associated configmap is updated and it needs to be done manually. This can lead to issues where the expected configuration for an environment differs from what's actually there. To allow for quicker iterations on the configuration the helm charts should support automatic rolling of the statefulsets.
Proposed Solution
Allow for an optional annotation that uses helm's ability to automatically roll deployments. For example, this can be set under the controller annotations here.
templates/controller/statefulset.yaml
...annotations:
{{- if .Values.controller.automaticReload.enabled }}checksum/config: {{ include (print $.Template.BasePath "<configmap-dir>") . | sha256sum }}{{ toYaml .Values.controller.podAnnotations | indent 8 }}
Background
Currently, the helm charts don't roll the corresponding pods for a given statefulset when an associated configmap is updated and it needs to be done manually. This can lead to issues where the expected configuration for an environment differs from what's actually there. To allow for quicker iterations on the configuration the helm charts should support automatic rolling of the statefulsets.
Proposed Solution
Allow for an optional annotation that uses helm's ability to automatically roll deployments. For example, this can be set under the controller annotations here.
templates/controller/statefulset.yaml
values.yaml
The text was updated successfully, but these errors were encountered: