Impossibility to configure child agent nodes differently (for A/B testing, progressive alert rollout, etc)
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 177
- Forks
- 81
- Avg merge
- 5h 48m
- Merged PRs (30d)
- 5
Description
We’re trying to configure parent.configs with different user configuration files for a subset of nodes, to achieve partial rollout of a change in alarm notification settings; we have a big cluster and don’t want to switch on this change in all nodes at once.
Is that possible with chart config options?
Can we patch config for certain nodes if not possible with helm chart?
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 by reviewing the Helm chart configuration options for parent.configs and how user configuration files are applied to child agent nodes. Determine whether node-specific configuration or patching is supported, and document the available approach or the scope of a chart change needed for partial rollout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100