operator-framework / operator-framework/java-operator-sdk
Removing update/patch methods from `UpdateControl`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
For v6 we should consider removing the methods from UpdateControl like patchStatus , patchResource etc.
The reason is that it could be rather confusing how those methods exactly do in the background, since we have flags to control their behavior - if they should use Server Side Apply or not for example.
Users can use the directly the Kubernetes client and/or utilities like PrimaryUpdateAndCacheUtils.
We might want to also rename UpdateControl to ReconcileControl.
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 UpdateControl and its patchStatus and patchResource methods, then compare their behavior and flags with the Kubernetes client and PrimaryUpdateAndCacheUtils. Done would require a settled v6 decision on removing those methods and possibly renaming UpdateControl to ReconcileControl.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100