Course contentsShow
← Cloud and Infrastructure
Lesson 1497 of 2,98930. Managed Kubernetes ServicesFree lesson

Connecting to AKS with kubectl

Using az aks get-credentials to configure kubectl access and authenticate to the cluster.

Connecting to AKS with kubectl

What you'll learn: How to authenticate and connect your local kubectl client to an Azure Kubernetes Service cluster using Azure CLI credentials.

Why This Matters

You've created an AKS cluster in Azure, but it's running in the cloud—how do you actually talk to it from your local machine? Unlike setting up kubectl for a self-managed cluster where you manually configure certificates and endpoints, AKS makes this dramatically simpler through integrated Azure authentication.

The az aks get-credentials Command

The Azure CLI provides a single command that does all the heavy lifting:

az aks get-credentials --resource-group myResourceGroup --name myAKSCluster

What happens behind the scenes:

  1. Fetches cluster details - retrieves the API server endpoint and cluster CA certificate
  2. Configures authentication - sets up Azure AD-based authentication using your current Azure login
  3. Updates kubeconfig - merges this configuration into your ~/.kube/config file (or creates it if it doesn't exist)
  4. Sets context - automatically switches kubectl to use this new cluster

Think of it like getting a keycard to a building—the command provisions your credentials and tells your kubectl client exactly where to go and how to prove who you are.

Using Your Connection

After running the command, you can immediately use kubectl:

kubectl get nodes
kubectl get pods --all-namespaces

The authentication happens transparently through your Azure identity. No manual certificate management needed!

Multiple Clusters

Each time you run get-credentials for a different cluster, it adds another context to your kubeconfig. Switch between them using kubectl config use-context.

Key Takeaway: The az aks get-credentials command configures kubectl with all necessary credentials and endpoints to securely connect to your AKS cluster, leveraging your existing Azure authentication—no manual certificate configuration required.