RBAC Migration Followup #26: Possible improvements to policy commands
Open
Nobody has claimed this yet.
help wanted
lifecycle/frozen
priority/P2
sig/security
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
- They should not fail on conflicts (should retry)
- They should constrain their delete operations to UID + RV matches
Contributor guide
No contributing guide indexed for this repository
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 policy command entry points and reviewing the RBAC migration context. Check existing tests for conflict handling and delete behavior, then define coverage for retries and UID/RV-constrained deletes before making the changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100