Skip to content
This repository has been archived by the owner on Jul 25, 2022. It is now read-only.

some gardenctl logs xxx commands failed in oidc env due to missing permissions #426

Open
neo-liang-sap opened this issue Nov 5, 2020 · 0 comments
Assignees
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@neo-liang-sap
Copy link
Contributor

neo-liang-sap commented Nov 5, 2020

Describe the bug
In OIDC enabled env, gardenctl logs command failed at (at least, not fully verified for other commands) follow parameter

gardenctl logs gardener-apiserver
gardenctl logs gardener-controller-manager
gardenctl logs gardener-dashboard
gardenctl logs etcd-operator

To Reproduce
Steps to reproduce the behavior:

  1. Which target was set 'gardenctl get target'
gardenctl get target                                                                                   
target:
- kind: garden
  name: dev
- kind: project
  name: sretestneo
- kind: shoot
  name: neo-test-ar
  1. Which command was entered [e.g. 'gardenctl show vpn-seed']
    gardenctl logs gardener-apiserver
    gardenctl logs gardener-controller-manager
    gardenctl logs gardener-dashboard
  2. What was the output of the command
    pods is forbidden: User "[email protected]" cannot list resource "pods" in API group "" in the namespace "garden"

Expected behavior
the logs should be displayed without error
Screenshots
image

Gardenctl Version (please complete the following information):
latest version on master branch

Additional context

@jguipi jguipi self-assigned this Feb 11, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

3 participants