Closed devonsams closed 1 year ago
I see I can use KubectlRawRestClient
, that will work.
As far as the lack of exec
support, I believe the suggestion would be getting it implemented 😆
It's a TODO in the code and maybe shouldn't be crazy to write up:
I can do my own pass on this, but in the meantime, KubectlRawRestClient
should be a fine workaround as you said.
Existing tracking issue for proper exec
support:
I've released rudimentary exec:
support in KubeConfigRestClient
in tag v0.5.1
. I did not test it with Azure Kubernetes, but given that Azure uses a DNS name for the control plane URL, KubeConfigRestClient
should be able to connect now (in addition to KubectlRawRestClient
)
I was wondering if there are suggestions for working around lack of
exec
support. I'm trying to connect to a cluster in Azure and my kube config uses thekubelogin
command viaexec
. Any ideas?