Closed MichaelSp closed 6 months ago
Hi, yes, currently it always tries to get the landscape-identity
from the config map, no matter if an alternative landscape name is given. That should be fixed.
Thanks for reporting.
Hi, as I have left the Gardener team at SAP, I don't have access to a Gardener installation any more. This means that I wont be able to provide a fix that works with enough assurance here. I know that many Gardener users use gardenctl
which I encourage everyone to also try (though I still preferred using kubeswitch over gardenctl during my time at SAP due to having one place for all of my kubeconfigs).
AFAIK the Gardener integration in kubeswitch still works at this moment in time but probably won't be developed further (at least not by me) - so I'll close this issue for now.
If people report that the integration is fundamentally broken for newer Gardener versions, I'll deprecate Gardener support.
I've configured gardener with the following options:
The WARN message:
store "gardener.landscape-live" returned an error during the search: failed to initialize store. This is most likely a problem with your provided kubeconfig: unable to get gardener landscape identity from config map kube-system/cluster-identity: configmaps "cluster-identity" is forbidden: User "my@email.com" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
Why does kubeswitch want to lookup the
cluster-identity
? That's already in the config.