AKS

AKS

If you are running the make targets locally, be sure to have met the Local requirements.

Preparation

You need to have a local ssh-agent with your key added for terraform to be able to add it to the created nodes:

eval "$(ssh-agent)"
ssh-add your_keyfile

Getting a AKS cluster configured for CAP

$> BACKEND=aks \
   AZURE_DNS_JSON=<abs path to a json containing the principal creds able to change DNS zones> \
   AZURE_RESOURCE_GROUP=<name of the resource group to be created> \
   AZURE_DNS_RESOURCE_GROUP=<name of an existing resource group with dns domain names configured>  \
   AZURE_APP_ID=<Azure client id> \
   AZURE_PASSWORD=<Azure client secret> \
   AZURE_TENANT_ID=< Tenant Id of your Azure SP> \
   AZURE_SUBSCRIPTION_ID=<Subscription Id of your Azure SP> \
   make k8s

Note that AZURE_TENANT_ID and AZURE_SUBSCRIPTION_ID are required for using it via a Service Principal. For details see: https://www.terraform.io/docs/providers/azurerm/guides/service_principal_client_secret.html#configuring-the-service-principal-in-terraform

This target leverages CAP-Terraform to deploy an AKS cluster prepared for CAP.

The target downloads all needed azure-cli binaries and sets them up in buildir/*.

Destroying the deployment of AKS

Since the infrastructure is living on AKS, instead of deleting the corresponding build folder, please run:

$> BACKEND=aks \
   AZURE_DNS_JSON=<abs path to a json containing the principal creds able to change DNS zones> \
   AZURE_RESOURCE_GROUP=<your personal resource group in azure> \
   AZURE_DNS_RESOURCE_GROUP=susecap-domain \
   make k8s

Deploying AKS and CAP on top

Same procedure, but call make all