Daniel Pacrami

Yes, I understand the issue and the background for it, however, constantly producing warnings whenever using an OIDC kubeconfig is distracting and can also be confusing. When we look at...

It may be good to evaluate how many times we are using curl/kubectl and evaluate if we need to split this into two tasks

At a minimum it would be great to be able to parse just the error messages. Some logs use the format of starting error messages with `E...` and some arbitrary...

Closing this issue in favor of https://github.com/gardener/gardenctl/issues/252

> I disagree. This one is opened for enhancement to prevent resource leakage, while #252 is about handling of already leaked resources which would have been unnecessary if resources do...

Some comments on this in a related issue: https://github.com/gardener/gardenctl/pull/263/files#r473192089

We can't use the oidc kubeconfigs with the CICD as the 2-factor is meant for humans (not automation). We would need a normal kubeconfig with sufficient permissions to perform these...

@tedteng you're totally right that we need to focus on adding more comprehensive testing but I agree with @neo-liang-sap regarding the subcommands - anything that directly calls a 3rd party...

For the temporary testing, those are good 👍 The same can apply for `kubectx`, `terraform` and `kubectl`

This may not be possible due to the fact that the loki pod is running on the seed and we get the logs by exec'ing into that pod and curling...