Clean up collision error format and provide context specifc error in the case of duplicate package installation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- go
- Domain
- infrastructure
Research direction
Start with the duplicate package installation regression e2e test discussed in PR #2764 and trace the existing COS conflict handling. Compare the proposed existing-ClusterExtension check with conflict detection, including the possible race. Done means duplicate installation has a concise, context-specific error without obscuring other resource conflicts.
Written by the indexing model from the issue text.
Description
The discussion in the PR introducing a duplication package installation regression e2e test, the suggestion was given that a better more context specific error message be provided for the user in the case of duplicate package installation.
As things are now, duplicate package installation is detected through the COS conflict behavior. Resource conflicts can happen in different contexts, e.g. preexisting cluster resources, foreign controller resource takeover, etc.
We could address duplicate installation through a check against existing CEs even before engaging with the resolver (although there could be an inherent race condition here that would put the onus anyway on conflict detection). We should also consider compressing the conflict error message as it is quite verbose and perhaps detect somehow whether the conflict is related to attempting to install a package that is already being handled by another ClusterExtension.
- Dominant language
- Go
- Stars
- 213
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 36
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.
More from operator-framework/operator-controller
-
lifecycle/stale
Difficulty 1/5 Under an hour Newbie friendliness 90/100
operator-framework/operator-controller#2726 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
epic epic/v1-api lifecycle/stale v1.x
Difficulty 5/5 Over a week Newbie friendliness 30/100
operator-framework/operator-controller#2727 · 2 comments ·
-
operator-framework/operator-controller#2686 · 2 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
operator-framework/operator-controller#2680 · 2 comments · 1 reaction ·
All issues in operator-framework/operator-controller
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·