kubernetes-sigs / kubernetes-sigs/secrets-store-sync-controller
Helm: add podDisruptionBudget
- Dominant language
- Go
- Stars
- 60
- Forks
- 21
- Avg merge
- 27m
- Merged PRs (30d)
- 3
Description
**Describe the solution you'd like**
The helm chart should include an explicit podDisruptionBudget to ensure the required availability of the controller is specified.
**Anything else you would like to add:**
A PDB that says all pods can be down is still useful because it is explicit.
**Environment:**
- Secrets Store Sync Controller version: (use the image tag): 0.0.2
- Kubernetes version: (use `kubectl version`): 1.33.0
Contributor guide
Research direction
Start by locating the Helm chart and its templates, then inspect how Kubernetes resources are defined and validated. Add an explicit PodDisruptionBudget for the controller, allowing all pods to be down as requested, and render or test the chart to confirm the resource is included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100