posit-dev / posit-dev/team-operator
team-operator: Auto-restart pods on ConfigMap/Secret changes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Summary
Watch ConfigMaps and Secrets for changes and trigger pod restarts when configuration changes.
Context
From README TODO:
- "What about configmaps changing, secrets changing, etc.? Can you watch / subscribe to changes in those?"
- "Related... migrating volumes, restarting the service / deployment when configmaps change, etc."
Approach Options
- Hash annotation: Add configmap/secret content hash as pod annotation, triggering rollout on change
- Reloader: Use external tool like stakater/Reloader
- Controller watches: Add watches for ConfigMaps/Secrets and trigger reconciliation
Acceptance Criteria
- Pods automatically restart when mounted ConfigMaps change
- Pods automatically restart when mounted Secrets change
- Document the chosen approach
Migrated from rstudio/ptd#2668
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 with the README TODO and compare the three proposed approaches: hash annotations, an external reloader, and controller watches. Determine which approach fits this Kubernetes operator, then implement and document it; done means mounted ConfigMaps and Secrets both trigger automatic pod restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100