influxdata / influxdata/helm-charts
Add support for podAnnotations helm rollme and/or checksum/config
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 257
- Forks
- 347
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 9
Description
Hi,
as in helm official docs (https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments), rollme and checksum/config annotations can be used in order to restart pod after a helm upgrade or configmap changes.
Currently, it is not possible to specify via values.yaml "rollme: {{ randAlphaNum 5 | quote }}" and "checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}" while they contain templating function that cannot be specified in values file.
I would suggest to add "rollme: {{ randAlphaNum 5 | quote }}" in spec.template.metadata.annotations field in statefulset.yaml influxdb2 chart template and use a boolean value in values.yaml (rollme for example) for controlling this annotation.
This could be very useful.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the influxdb2 chart's statefulset.yaml template and values.yaml. Check how spec.template.metadata.annotations is currently defined, then review the Helm chart behavior for rollme and checksum/config annotations. Done means a configurable annotation mechanism is supported and the chart renders the expected StatefulSet metadata after a Helm upgrade or ConfigMap change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100