carvel-dev / carvel-dev/kapp-controller
add condition to indicate constant reconciliation drift
Open
discussion
enhancement
- Dominant language
- Go
- Stars
- 323
- Forks
- 127
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 6
Description
it might be helpful to indicate that resources are consistently drifting. it should probably kick in if we see that X number of consecutive reconciliations happened without external change (though how does one no what is external...).
Contributor guide
Research direction
Start by locating the reconciliation logic and how resource conditions are currently reported. Before implementation, clarify the consecutive-reconciliation threshold and how external changes are identified; done should include an agreed condition that reliably indicates persistent drift and coverage for the relevant reconciliation behavior.
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
- Needs clarification
- Newbie friendliness
- 25/100