You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a Kubernetes context is configured with proxy-url you are unable to add a Kubernetes provider. When going to add a provider:
Click Kubernetes
See the "Loading Kubernetes ...."
Infinite spinner
kubectl commands work but the client for Devpod is not using this setting correctly.
What did you expect to happen instead?
The Kubernetes provider is able to be configured.
How can we reproduce the bug? (as minimally and precisely as possible)
Setup a Kubernetes configuration. (In this case it was an aws eks update-config based configuration with the external credential provider command updated to give the full path to the aws command.)
Modify the configuration to use a proxy:
kubectl config set clusters.$context_name.proxy-url socks5://localhost:$port
Create the tunnel:
ssh -D $port user@bastion
See that kubectl is working as expected.
See that you can no longer add a Kubernetes provider in Devpod.
Local Environment:
DevPod Version: v0.6.6
Operating System: mac
ARCH of the OS: ARM64
DevPod Provider:
Cloud Provider: aws
Kubernetes Provider: client 1.22, server 1.29+
Anything else we need to know?
The text was updated successfully, but these errors were encountered:
What happened?
When a Kubernetes context is configured with
proxy-url
you are unable to add a Kubernetes provider. When going to add a provider:kubectl
commands work but the client for Devpod is not using this setting correctly.What did you expect to happen instead?
The Kubernetes provider is able to be configured.
How can we reproduce the bug? (as minimally and precisely as possible)
aws eks update-config
based configuration with the external credential provider command updated to give the full path to theaws
command.)kubectl
is working as expected.Local Environment:
DevPod Provider:
Anything else we need to know?
The text was updated successfully, but these errors were encountered: