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

AKS Get-credentials does not respect KUBECONFIG env var #18700

Closed
Volatus opened this issue Jun 30, 2021 · 2 comments · Fixed by #18704
Closed

AKS Get-credentials does not respect KUBECONFIG env var #18700

Volatus opened this issue Jun 30, 2021 · 2 comments · Fixed by #18704
Labels
AKS az aks/acs/openshift Service Attention This issue is responsible by Azure service team.

Comments

@Volatus
Copy link
Contributor

Volatus commented Jun 30, 2021

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
az aks get-credentials runs fine but writes only to /Users/xs/.kube/config despite export KUBECONFIG=$HOME/.config/kube/config. Yes, the specified KUBECONFIG file does exist and even has 4 contexts in it.

To Reproduce
az aks get-credentials -n <cluster name> -g <resource group>. I currently have 4 other contexts in my KUBECONFIG.

Expected behavior
The new config for the cluster should be added to the existing kubeconfig file.

Environment summary
Installed with brew on M1 MacBook. (darwin/arm64, BigSur)
az version:

{
  "azure-cli": "2.25.0",
  "azure-cli-core": "2.25.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {}
}

kubectl version --client:

Client Version: version.Info{
Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:52:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"darwin/arm64"
}
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 30, 2021
@yonzhan yonzhan added the AKS az aks/acs/openshift label Jul 1, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jul 1, 2021
@yonzhan yonzhan added Service Attention This issue is responsible by Azure service team. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jul 1, 2021
@ghost
Copy link

ghost commented Jul 1, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.

Issue Details

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
az aks get-credentials runs fine but writes only to /Users/xs/.kube/config despite export KUBECONFIG=$HOME/.config/kube/config. Yes, the specified KUBECONFIG file does exist and even has 4 contexts in it.

To Reproduce
az aks get-credentials -n <cluster name> -g <resource group>. I currently have 4 other contexts in my KUBECONFIG.

Expected behavior
The new config for the cluster should be added to the existing kubeconfig file.

Environment summary
Installed with brew on M1 MacBook. (darwin/arm64, BigSur)
az version:

{
  "azure-cli": "2.25.0",
  "azure-cli-core": "2.25.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {}
}

kubectl version --client:

Client Version: version.Info{
Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:52:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"darwin/arm64"
}
Author: Volatus
Assignees: -
Labels:

AKS, Service Attention

Milestone: -

@yonzhan
Copy link
Collaborator

yonzhan commented Jul 1, 2021

route to service team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AKS az aks/acs/openshift Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants