[BUG] Our reconciliation logic is not handling a field removal from CR
Open
Nobody has claimed this yet.
bug
go-alpha
prio-list
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Our reconciliation logic is not handling a resource removal from CR, it is only checking if what is defined is deployed.
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 reconciliation logic for resources defined in the custom resource and trace how it compares desired and deployed state. Reproduce a field removal from the custom resource, then verify that the corresponding deployed resource is removed or updated; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100