Create a per pod status resource so we can validate the state of all pods during tests and in production envs
Open
Nobody has claimed this yet.
enhancement
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
The per resource status is a lie - it is just the status of the current leader pod.
High level proposal:
- Add new CRDs that purely represent status
- Each pod creates its own instance of the CR with the pod as an owner ref
- Each pod maintains this status resource on a short (~one minute) timer (i.e. trigger by both watch events and by time)
- Each pod should only watch its own instance to avoid processing events from other pods
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, tests, or entry points are named in the issue. Start by locating the existing per-resource status implementation and its Kubernetes CRD definitions, then map how pods watch and update status; done means each pod owns and periodically maintains its own status resource, watches only that instance, and tests and production environments can validate all pod states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100