Deploy to Azure

Deploying Azure Kubernetes Service (AKS) using an Azure Resource Manager (ARM) template standardizes and automates the setup process. This guide outlines the prerequisites and provides instructions for deploying via the Azure Portal and Azure CLI, followed by installing your application.

Table of Contents

1. Deploy Infrastructure

2. Connect to Cluster

3. Install App

4. Next Steps

---

Prerequisites

Before deploying the AKS cluster, ensure you have the following:

1. Azure Subscription: An active Azure subscription. If you don't have one, you can create a free account.

2. Azure CLI: Installed on your local machine. Download it from here.

3. Permissions: Sufficient permissions to create resources in the desired Azure subscription and resource group.

---

Step 1: Deploy Infrastructure

Deploying the AKS cluster involves creating the necessary Azure resources. You can perform this step using either the Azure Portal or the Azure CLI.

Azure Portal

• Navigate to Azure Portal: Go to portal.azure.com and sign in.

• Create a Resource Group:

  • Search for "Resource groups" in the top search bar.

  • Click Add and provide:

    • Subscription: Select your Azure subscription.

    • Resource group: e.g., dev-sandbox.

    • Region: e.g., West US 2.

  • Click Review + create and then Create.

• Deploy the ARM Template:

  • Click Create a resource.

  • Search for and select Template deployment (deploy using custom templates).

  • Click Create and follow the prompts to upload your ARM template (aks-deployment-template.json).

• Monitor Deployment:

  • Check Notifications (bell icon) in the top-right corner until deployment completes successfully.

Azure CLI

• Clone Automation

  git clone https://github.com/opengovern/automation.git
  cd automation/product-install/azure/aks

• Open Terminal and Log in to Azure:

  az login

• Set Subscription (if needed):

  az account set --subscription "Your-Subscription-Name"

• Create a Resource Group:

  az group create --name dev-sandbox --location westus2

• Deploy the ARM Template:

  Ensure aks-deployment-template.json is in the current directory or provide its full path.

  az deployment group create \
    --resource-group dev-sandbox \
    --template-file aks-deployment-template.json \
    --name aksDeployment

• Monitor Deployment:

  The CLI will provide real-time feedback. Wait until the deployment completes successfully.

Step 2: Connect to Cluster

After deploying the infrastructure, verify the deployment to ensure everything is set up correctly.

Azure Portal

Using Azure Portal

1. Navigate to Resource Groups: Open your resource group (e.g., MC_dev_sandbox_westus2).

2. Check Resources: Confirm the presence of the AKS cluster, agent pools, and other associated resources.

3. Access AKS Cluster: Click on the AKS cluster (e.g., sandbox) to review settings like node pools, networking, security, and monitoring.

Second Tab

Using Azure CLI

1. List AKS Clusters:

   az aks list --resource-group dev-sandbox --output table

2. Get AKS Cluster Details:

   az aks show --resource-group dev-sandbox --name sandbox --output json

3. Connect to the AKS Cluster:

   az aks get-credentials --resource-group dev-sandbox --name sandbox

4. Verify Nodes:

   kubectl get nodes

   • Ensure nodes from your agent pool are listed.

Step 3: Install Application

With the AKS cluster deployed and verified, proceed to install your application using Helm.

helm repo add opencomply https://charts.opencomply.io
helm repo update
helm install opencomply opencomply/opencomply --create-namespace --namespace opencomply --timeout 10m

Monitor Installation:

• Use the following command to check the status of the Helm release:

  helm status opencomply -n opencomply

• Alternatively, monitor the pods in the namespace:

  kubectl get pods -n opencomply

• Wait until all pods are in the Running state.

For more detailed information, refer to the Azure Kubernetes Service Documentation.

---

Note: Always ensure that you follow best practices for security, cost management, and resource governance when deploying and managing your AKS clusters.