Closed danielfoehrKn closed 11 months ago
This change has been postponed to apply only for k8s v1.26, not v1.25, but it would be great to get this implemented sooner rather than later.
Is the gke-gcloud-auth-plugin
backward compatible? What I mean is: would it be safe to just make kubeswitch
convert all existing configs to the new format?
This is now in effect for 1.26 clusters at least. It's causing GKE commands to fail.
Similar to https://github.com/danielfoehrKn/kubeswitch/issues/67 I'm happy to offer a "bounty" of 50€ for anyone tackling this as an additional incentive.
Thank you @gjariv I've reached out via mail about the "bounty" if you're interested.
No thanks, appreciate it, but just happy to help and unblock people
Thank you very much! That, you did.
Today, when using the kubeconfig generated by kubeswitch with kubectl > 1.22, we get the following warning
Please see here for more information.
Currently, the user section of the kubeconfig is generated like so:
in the future it should look like so
gke-gcloud-auth-plugin
(must be installed on the client side!)