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

Check if the namespace is defined in all the kubernetes commands #375

Open
cbosdo opened this issue Jun 24, 2024 · 0 comments
Open

Check if the namespace is defined in all the kubernetes commands #375

cbosdo opened this issue Jun 24, 2024 · 0 comments
Assignees
Labels
bug Something isn't working Kubernetes Affects Kubernetes backend

Comments

@cbosdo
Copy link
Contributor

cbosdo commented Jun 24, 2024

The server and the proxy may be running in a kubernetes namespace that is not default. In such a case the namespace need to be looked for and set with -n namespace in the kubectl commands.
This has been ignored for a while and probably needs fixing in a few places.

Connection.Exec() should add the namespace automatically and Connection.GetPodName() should be able to retrieve the namespace too.

@cbosdo cbosdo added bug Something isn't working Kubernetes Affects Kubernetes backend labels Jun 24, 2024
@rjpmestre rjpmestre self-assigned this Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Kubernetes Affects Kubernetes backend
Projects
None yet
Development

No branches or pull requests

2 participants