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
when a user setups the az cli outside the home directory, e.g. in a jenkins env, the azurecli login in kubelogin will not be able to find the appropriate az context until AZURE_CONFIG_DIR is set. The idea is to enable convert-kubeconfig sub command to take this path and update kubeconfig so that get-token sub-command knows where the az context is
The text was updated successfully, but these errors were encountered:
This will be very useful for us, and probably other customers as well, reducing the overhead for carrying around the az-context to every kubectl command executed per AKS cluster in automation scripts, shared libraries or other CI/CD implementations.
when a user setups the az cli outside the home directory, e.g. in a jenkins env, the azurecli login in kubelogin will not be able to find the appropriate az context until
AZURE_CONFIG_DIR
is set. The idea is to enableconvert-kubeconfig
sub command to take this path and update kubeconfig so thatget-token
sub-command knows where the az context isThe text was updated successfully, but these errors were encountered: