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
{{ message }}
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.
Expected behaviour: When the current_context is set explictly using KubeConfig.set_current_context, and then further Kubernetes requests are made, Kubernetes requests are being made to new context that is set.
Actual behaviour: When the current_context is set explictly using KubeConfig.set_current_context, and then further Kubernetes requests are made, Kubernetes requests are being made to the context set in "kubeconfig" file.
Steps to reproduce (the current-context in my kube config file is test123):
Expected behaviour: When the
current_context
is set explictly usingKubeConfig.set_current_context
, and then further Kubernetes requests are made, Kubernetes requests are being made to new context that is set.Actual behaviour: When the
current_context
is set explictly usingKubeConfig.set_current_context
, and then further Kubernetes requests are made, Kubernetes requests are being made to the context set in "kubeconfig" file.Steps to reproduce (the current-context in my kube config file is test123):
Executing the above tries to fetch the configmap from the "test123" context and not from the "test42" context.
The text was updated successfully, but these errors were encountered: