kcp
kcp copied to clipboard
kcp-dev
Run End-to-end Tests With Minimal Permissions
Right now, we're not really testing all of the branches of the authorizer(s) and/or getting feedback on how normal users will need to interact with the system, as we're using the kcp-admin account (part of system:masters) to run all end-to-end tests.
We should instead create ServiceAccounts with explicit, minimal privileges for tests.
/cc @sttts @s-urbaniak @ncdc
Outside of the authorizer tests, we are basically going to benefit from unprivileged clients from a DX perspective.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kcp-ci-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.