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
Is your feature request related to a problem? Please describe.
When provisioning an AKS cluster with add-ons that are deployed via Helm charts, the az aks get-credentials command is included in the shell script or PowerShell script, as the user has to connect to the cluster to perform the final steps of installing those add-ons. This doesn't happen if no add-ons are selected, and the script stops after the command to provision the AKS cluster.
Describe the solution you'd like
It would be useful to always include the az aks get-credentials command with these scripts, or at least include an option to generate them, so users don't have to craft them manually or go looking for them in the Azure portal. It would be especially useful if creating multiple clusters in a short period of time, knowing that the cluster credentials are automatically added to your kubectl contexts.
Describe alternatives you've considered
Currently, I have to either craft these manually or go into the AKS portal and copy the command from the "Connect" button on the AKS cluster blade.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
pjlewisuk
changed the title
Always include get credentials command when provisioning via bash or PowerShell
Feature: Always include get credentials command when provisioning via bash or PowerShell
Jul 12, 2023
Is your feature request related to a problem? Please describe.
When provisioning an AKS cluster with add-ons that are deployed via Helm charts, the
az aks get-credentials
command is included in the shell script or PowerShell script, as the user has to connect to the cluster to perform the final steps of installing those add-ons. This doesn't happen if no add-ons are selected, and the script stops after the command to provision the AKS cluster.Describe the solution you'd like
It would be useful to always include the
az aks get-credentials
command with these scripts, or at least include an option to generate them, so users don't have to craft them manually or go looking for them in the Azure portal. It would be especially useful if creating multiple clusters in a short period of time, knowing that the cluster credentials are automatically added to yourkubectl
contexts.Describe alternatives you've considered
Currently, I have to either craft these manually or go into the AKS portal and copy the command from the "Connect" button on the AKS cluster blade.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: