Azure Kubernetes Service
Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you quickly deploy and manage clusters.
Last updated
Was this helpful?
Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you quickly deploy and manage clusters.
Last updated
Was this helpful?
If you don't have an , create an before you begin.
The identity you're using to create your cluster has the appropriate minimum permissions. For more details on access and identity for AKS, see .
You should also have and installed on your terminal application. You can also use the which will come with these utilities pre-installed.
If you plan to use your local terminal you will need to before we can connect to our cluster.
Sign in to the .
On the Azure portal menu or from the Home page, select Create a resource.
Select Containers > Kubernetes Service.
On the Basics page, configure the following options:
Project details:
Select an Azure Subscription.
Select or create an Azure Resource group, such as myResourceGroup.
Cluster details:
Ensure the the Preset configuration is Standard ($$). For more details on preset configurations, see .
Enter a Kubernetes cluster name, such as myAKSCluster.
Select a Region for the AKS cluster, and leave the default value selected for Kubernetes version.
Select 99.5% for API server availability.
Primary node pool:
Leave the default values selected
Select Next: Node pools when complete.
Keep the default Node pools options. At the bottom of the screen, click Next: Access.
On the Access page, configure the following options:
The default value for Resource identity is System-assigned managed identity. Managed identities provide an identity for applications to use when connecting to resources that support Azure Active Directory (Azure AD) authentication. For more details about managed identities, see
The Kubernetes role-based access control (RBAC) option is the default value to provide more fine-grained control over access to the Kubernetes resources deployed in your AKS cluster.
By default, Basic networking is used, and is enabled.
Click Review + create. When you navigate to the Review + create tab, Azure runs validation on the settings that you have chosen. If validation passes, you can proceed to create the AKS cluster by selecting Create. If validation fails, then it indicates which settings need to be modified.
It takes a few minutes to create the AKS cluster. When your deployment is complete, navigate to your resource by either:
Selecting Go to resource, or
Browsing to the AKS cluster resource group and selecting the AKS resource. In this example you browse for myResourceGroup and select the resource myAKSCluster.
To perform these operations in a local shell installation:
Verify the connection to your cluster using kubectl get to return a list of the cluster nodes.
Output shows the single node created in the previous steps. Make sure the node status is Ready:
An ingress controller is a piece of software that provides reverse proxy, configurable traffic routing, and TLS termination for Kubernetes services. Kubernetes ingress resources are used to configure the ingress rules and routes for individual Kubernetes services.
Download the above zip file to a directory onto your system, then use the following command to unzip the contents to a directory.
Copy the .example.env to .env then edit the contents with your deployment settings.
Next create an apps/ directory in the root of this project folder. This will be where we unpack helm charts to create deployments from.
Next step is to run the deployment scripts(s). This can be done with 1 deployment script or by running each script separately. Each script will prompt the user for information related to that scripts purpose.
Run the single script can be running bash scripts/deploy.sh
Run each individual script. Follow the code block below. See the README.md that was included with the zip file for details about each script.
When this has finished successfully you will see an terminal output for all of the services in this deployment.
For this section you will need to be either or to execute kubectl and helm command line tools.
Configure kubectl to connect to your Kubernetes cluster using the command. The following command downloads credentials and configures the Kubernetes CLI to use them.
In this section we will be using kubectl and helm to create deployment to a namespace on our AKS cluster. Since this is an Azure deployment we will be using for our PDF uploads, for our NoSQL database solution.
If the deployment is NOT showing on the domain that you configured as the BASE_URL environment variable you will most likely need to configure the DNS records. For this tutorial, we used , but can also be done with .
