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
I don't have any problem as such with current variable just that I frequently use KUBECONFIG to work with my cluster and think using same environment variable as k8s would provide a better experience with the provider 😃
The text was updated successfully, but these errors were encountered:
I wish you came up with that suggestion in my initial K8S PR 😄 - I was wondering if there any standardized ENV vars and I couldn't find any at that time.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 11, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To be consistent with K8s way of setting the config - https://kubernetes.io/docs/tasks/administer-cluster/share-configuration/, I think we should change the KUBE_CONFIG to KUBECONFIG here
I don't have any problem as such with current variable just that I frequently use KUBECONFIG to work with my cluster and think using same environment variable as k8s would provide a better experience with the provider 😃
The text was updated successfully, but these errors were encountered: