Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes proxy-url Not Being Used #1506

Closed
damaestro opened this issue Dec 23, 2024 · 2 comments
Closed

Kubernetes proxy-url Not Being Used #1506

damaestro opened this issue Dec 23, 2024 · 2 comments
Labels

Comments

@damaestro
Copy link

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:

  1. Click Kubernetes
  2. See the "Loading Kubernetes ...."
  3. 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)

  1. 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.)
  2. Modify the configuration to use a proxy:
kubectl config set clusters.$context_name.proxy-url socks5://localhost:$port
  1. Create the tunnel:
ssh -D $port user@bastion
  1. See that kubectl is working as expected.
  2. 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?

@damaestro
Copy link
Author

The infinite spinner is #1507

@damaestro
Copy link
Author

It appears that the proxy-url setting does work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant