Set up consistent `securityContext` 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
Extension of #195 and considering the pattern set up by #198
- ensure all products have
pod.containerSecurityContextandpod.securityContext - set up a backwards-compatible mechanism for notifying users / allowing them to switch over (deprecate, etc.)
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 issues #195 and #198, then inspect the product Helm charts and their existing pod security settings. Confirm that every product exposes both requested fields and define how users are notified of, and can transition from, the previous configuration without breaking existing deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100