Deploy Domino on AKS

Use the information in this section to deploy Domino components in the Azure infrastructure.

Use the environment variables to set the values of IDs, names, and labels in your Azure environment. This simplifies the commands that you will use when installing the Domino components.

export SUB_ID=<ID of the subscription where AKS was deployed>
export RG_NAME=<Name of the resource group where AKS was deployed>
export CLUSTER_NAME=<AKS cluster name>
export DOMINO_VER=<Domino version to deploy>
export QUAY_USERNAME=<quay.io username provided by Domino>
export QUAY_PASSWORD=<quay.io password provided by Domino>

Note

Gather the required parameters which you will add to the domino.yaml file when you enter the environment parameters in the configuration template.

TENANT_ID: ID of the tenant where AKS was deployed.
IMAGE_BUILD_CLIENT_ID: The image building client id created by terraform.
IMAGE_BUILD_WORKLOAD_IDENTITY: Whether the image build client id is a workload identity.
REG_DNS_NAME: The DNS name of the container registry created by terraform in the AKS resource group.
STORAGE_ACCOUNT_NAME: The name of the storage account created by terraform in the AKS resource group.
STORAGE_ACCOUNT_KEY: The key of the storage account created by terraform in the AKS resource group.
STORAGE_ACCOUNT_CONTAINER_NAME: The name of the container in the storage account created by terraform in the AKS resource group.

To retrieve credentials for the Kubernetes cluster, run the following command to add the AKS credentials to your kubectl config file:
```
az aks get-credentials --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME
```
To create the domino-platform namespace, run:
```
kubectl create namespace domino-platform
```
To set up your HTTPS certificate, run the following command to create a secret that uses the certificate for the domain name. This domain name allows the Domino management plane to be accessible through HTTPS:
```
kubectl -n domino-platform create secret tls my-cert --key=<path to your private key> --cert=<path to your cert>
```

The fleetcommand-agent runs as a container. It installs and configures Domino components. The fleetcommand-agent uses an installation template to gather the required parameters for the environment and sets them when installing Domino components.

The installation process with fleetcommand-agent generates a blank installation template where you enter your environment parameters and then provide them to fleetcommand-agent to perform the installation tasks.

Generate a blank installation template with fleetcommand-agent:

If you aren’t logged into quay.io, execute: docker login -u $QUAY_USERNAME -p $QUAY_PASSWORD quay.io

Run the following command to generate a domino.yml template configuration file in the current working directory.

Note	This overwrites any existing `domino.yml` file.

docker run --rm -it
  -v $(pwd):/install
  quay.io/domino/fleetcommand-agent:5.11.3.catalog-8cb5e60
  init --file /install/domino.yml --version $DOMINO_VER --preset aks