Provision Cluster and Fetch Credentials
A 3-step recipe with Azure Kubernetes Service. We can help you get access.
Recipe · 3 steps
Provision Cluster and Fetch Credentials
with Azure Kubernetes Service · IT Infrastructure Management
Create an AKS managed cluster, wait for it to finish provisioning, and pull admin credentials.
- Submit a managed cluster create-or-update request. ARM wraps cluster configuration under a properties object and returns 201 Created for an asynchronous provision.
- Read the cluster and inspect provisioningState. While the cluster is still Creating the flow loops back to this step; once it reports Succeeded the flow advances to retrieve credentials.
- List the cluster admin credentials. The response carries a kubeconfigs array whose first entry holds the base64-encoded kubeconfig for the new cluster.
What you'll need to have ready
- subscriptionId: The ID of the target subscription (valid UUID).
- resourceGroupName: The name of the resource group.
- resourceName: The name of the managed cluster to create.
- location: The Azure region for the cluster (e.g. eastus).
- apiVersion: The AKS REST API version to use.
- dnsPrefix: The DNS prefix for the cluster API server.
- kubernetesVersion: The Kubernetes version to deploy.
- nodeCount: The initial node count for the default system pool.
- vmSize: The VM size for the default system pool nodes.
- accessToken: An Azure AD bearer token with user_impersonation scope.
For your developer
Arazzo workflow microsoft-azure-kubernetes-service:provision-cluster-and-fetch-credentials, 3 operations: ManagedClusters_CreateOrUpdate → ManagedClusters_Get → ManagedClusters_ListClusterAdminCredentials. Specs on APIs.io.