azure-cli
azure-cli copied to clipboard
az aks get-credentials --format "exec" default to azurecli?
Related command az aks get-credentials --format "exec"
Is your feature request related to a problem? Please describe.
After the release of kubelogin and the deprecation of Azure credentials. I assume most people use azurecli token as their default access . Today the --format "exec"
defaults to device code.
Describe the solution you'd like
Instead of being forced to do a kubeconfig convert, I would like to have azure cli as the default.
Describe alternatives you've considered
either change the --format "exec"
to be azure CLI, or allow other formats so we can choose what method we want to use without the convert
route to CXP team
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.
Issue Details
Related command az aks get-credentials --format "exec"
Is your feature request related to a problem? Please describe.
After the release of kubelogin and the deprecation of Azure credentials. I assume most people use azurecli token as their default access . Today the --format "exec"
defaults to device code.
Describe the solution you'd like
Instead of being forced to do a kubeconfig convert, I would like to have azure cli as the default.
Describe alternatives you've considered
either change the --format "exec"
to be azure CLI, or allow other formats so we can choose what method we want to use without the convert
Author: | ehrnst |
---|---|
Assignees: | - |
Labels: |
|
Milestone: | - |
@Azure/aks-pm Could you please look into this request and provide some pointers ? Thanks in advance.
would also prefer to use "azurecli" as default or an option to provide the needed "exec" format
IMO az aks get-credentials
should set up the kubeconfig to use the default credentials of the already signed in azure cli. How someone logs into azure cli using az login
is up to them. But I doubt anyone wants this set to device code, that should be an override option if needed.
Perhaps this should follow a similar pattern to the DefaultAzureCredential Class?
If the instructions always involve running kubelogin convert-kubeconfig -l azurecli
then why not just set it up right in the first place? Adding an additional step is unintuitive.
Is this still relevant? i'm not sure if we still need to do the convert dance, or not, I just do it (hopefully) out of old habits.