Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default access role is denied to list pods #20401

Closed
tigrato opened this issue Jan 19, 2023 · 0 comments · Fixed by #20402
Closed

Default access role is denied to list pods #20401

tigrato opened this issue Jan 19, 2023 · 0 comments · Fixed by #20402
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan

Comments

@tigrato
Copy link
Contributor

tigrato commented Jan 19, 2023

Expected behavior:
kubectl get pods should work for users with access role.

Bug details:

  • Teleport version: 12
@tigrato tigrato added the bug label Jan 19, 2023
tigrato added a commit that referenced this issue Jan 19, 2023
This PR adds full access to `pod` resources on every namespace for
default role `access`.

Fixes #20401
@codingllama codingllama added test-plan-problem Issues which have been surfaced by running the manual release test plan platform-security and removed platform-security labels Jan 19, 2023
tigrato added a commit that referenced this issue Jan 19, 2023
This PR adds full access to `pod` resources on every namespace for
default role `access`.

Fixes #20401
github-actions bot pushed a commit that referenced this issue Jan 19, 2023
This PR adds full access to `pod` resources on every namespace for
default role `access`.

Fixes #20401
tigrato added a commit that referenced this issue Jan 20, 2023
This PR adds full access to `pod` resources on every namespace for
default role `access`.

Fixes #20401
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants