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
satishweb
changed the title
Helm command failure: Kubernetes cluster unreachable: context "my-aws-k8s-context-name" does not exist
Helm command failure: Kubernetes cluster unreachable: context does not exist
Mar 18, 2024
Root cause: HOME variable was declared in the devspace.yaml and that caused changes to the devspace runtime environment. Removing HOME variable resolved the error
If the debug flag was passed to the helm command, this root cause could have been clearer. #2846 is added for this feature request.
What happened?
devspace dev
command failed with below error:What did you expect to happen instead?
devspace dev successfully executing helm command to install the helm chart
How can we reproduce the bug? (as minimally and precisely as possible)
devspace dev
My devspace.yaml:
Local Environment:
Kubernetes Cluster:
Anything else we need to know?
Apparently, failure was caused by use of HOME var declaration. Renaming HOME to CONTAINER_HOME solved the problem.
It took a while to figure out the root cause. If --debug flag was passed to the helm command, it would have been more easier to find the root cause.
The text was updated successfully, but these errors were encountered: