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

kurtosis always uses default k8s context #2615

Open
0x416e746f6e opened this issue Jan 2, 2025 · 0 comments
Open

kurtosis always uses default k8s context #2615

0x416e746f6e opened this issue Jan 2, 2025 · 0 comments
Labels
bug Something isn't working cli For bugs relating to the CLI painful Painful bug

Comments

@0x416e746f6e
Copy link

0x416e746f6e commented Jan 2, 2025

What's your CLI version?

1.4.3

Description & steps to reproduce

If there's more than 1 cluster configured on the machine, and kurtosis is being set to use a non-default one with kurtosis cluster set command, then it will nevertheless use the default one.

Desired behavior

Correct cluster should be used.

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

CLI: the Command Line Interface

@0x416e746f6e 0x416e746f6e added the bug Something isn't working label Jan 2, 2025
@github-actions github-actions bot added cli For bugs relating to the CLI painful Painful bug labels Jan 2, 2025
@0x416e746f6e 0x416e746f6e changed the title kurtosis doesn't respect KUBECONFIG env variable kurtosis always uses default k8s context Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cli For bugs relating to the CLI painful Painful bug
Projects
None yet
Development

No branches or pull requests

1 participant