zalando-incubator / zalando-incubator/stackset-controller
Make it possible to verify whether resources were updated or not
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
It's impossible to figure out whether the controller has processed the changes and updated the resources or not. The following information needs to be exposed so it's possible to figure out if the updates are done or still in progress:
observedGenerationinStackset.status, updated only after the changes to the stacks are doneobservedGenerationonStack.status, updated only after the subresources have been changedcurrentStackNameinStackset.statusto avoid duplicating the weirddefaultand name generation logic
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 locating the Stackset.status and Stack.status definitions and tracing the controller reconciliation path that updates stacks and subresources. Verify how the current stack name is generated, then identify the status update points; done means both observedGeneration fields reflect completed work and currentStackName is exposed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100