Is your feature request related to a problem? Please describe.
Currently the Helm chart does not allow users to add custom annotations to the resulting Secret and Deployment manifests that get rendered during installation/upgrade.
Annotations are useful for integrating with tools like stakater/reloader which watch annotated resources and trigger rollouts when they change (e.g., reload certs on secret update). Without this capability, users must patch manifests post-render or restart deployment manually.
Describe the solution you'd like
Add optional configuration in values.yaml to let consumers specify arbitrary annotations for:
- the generated Certificate Secret
- the Deployment resource
For example:
deploymentAnnotations:
reloader.stakater.com/search: "true"
secretAnnotations:
reloader.stakater.com/match: "true"
The chart templates should include the provided annotations under metadata.annotations for each resource only when defined.
Describe alternatives you've considered
- Using a post-renderer tool or kustomize overlay — adds complexity and extra tooling.
- Forking the chart and maintaining custom templates — creates maintenance overhead.
- Rely on external automation (e.g., ArgoCD ApplicationSet annotations) — doesn’t cover all use cases and depends on the delivery tool.
Additional context
This change would make it easier to support auto-reload patterns (like stakater/reloader) and other annotation-based tooling without requiring users to manipulate the rendered output or maintain chart forks.
PR for this is ready for review: #25
Is your feature request related to a problem? Please describe.
Currently the Helm chart does not allow users to add custom annotations to the resulting Secret and Deployment manifests that get rendered during installation/upgrade.
Annotations are useful for integrating with tools like
stakater/reloaderwhich watch annotated resources and trigger rollouts when they change (e.g., reload certs on secret update). Without this capability, users must patch manifests post-render or restart deployment manually.Describe the solution you'd like
Add optional configuration in values.yaml to let consumers specify arbitrary annotations for:
For example:
The chart templates should include the provided annotations under metadata.annotations for each resource only when defined.
Describe alternatives you've considered
Additional context
This change would make it easier to support auto-reload patterns (like stakater/reloader) and other annotation-based tooling without requiring users to manipulate the rendered output or maintain chart forks.
PR for this is ready for review: #25