Ensure consistency in helm values across charts
Open
Nobody has claimed this yet.
consistency
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
We should have a portion of CI that ensures we are aware when we add new values
(Not sure if this is do-able via CI...)
- detect if similar values are used? (i.e.
serviceAccountNamevs.serviceAccount.name) - aggregate values keys across charts
- aggregate default values across charts (for shared keys)
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
No files, charts, or tests are named. Start by inventorying the Helm charts and their values, then determine how CI could aggregate keys and shared defaults while identifying similarly named values such as serviceAccountName and serviceAccount.name. Done means the consistency checks and their expected CI behavior are defined and verified across the charts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100