kubernetes-sigs / kubernetes-sigs/controller-runtime
It would be nice to run integration tests as SA used to run the controller normally
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3k
- Forks
- 1.3k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 14
Description
Currently, integration tests don't run as the SA used to launch the controllers normally (in kubebuilder and similar tools), so we can't catch RBAC issues in integration tests. It would be nice to integrate support for alternate SAs into our test environment.
Potential blocker: the SA token controller isn't running, so we can't use token-based SAs.
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 tracing the integration-test environment and how controllers are currently launched, then investigate how alternate service accounts and the SA token controller fit into that setup. Done means integration tests can run controllers under alternate SAs and expose RBAC issues, with the token-based SA limitation addressed or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100