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

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

docker run --rm -it \
  -v $(pwd):/install \
  quay.io/domino/fleetcommand-agent:v54 \
  init --file /install/domino.yml --version $DOMINO_VER

Note

Enter your environment parameters into the configuration template:

Open the domino.yml file and edit the attributes as follows:
- name: The name to give the deployment. This cannot be changed after deployment.
- hostname: Hostname for the Domino install (for example, domino.example.com).
- pod_cidr: 10.0.0.0/8 for the default Azure vnet, but this should match the full IP range that your cluster uses.
- storage_classes.block.type: azure-disk
- storage_classes.shared.type: azure-file
- blob_storage.projects.type: shared
- blob_storage.logs.type: shared
- blob_storage.backups.type: shared
- blob_storage.backups.azure.account_name: STORAGE_ACCOUNT_NAME value
- blob_storage.backups.azure.account_key: STORAGE_ACCOUNT_KEY value
- blob_storage.backups.azure.container: STORAGE_ACCOUNT_CONTAINER_NAME value
- helm.cache_path: /app/charts
- private_docker_registry.username: <Your quay username>
- private_docker_registry.password: <Your quay password>
- internal_docker_registry.enabled: false
- external_docker_registry: Set to container registry DNS name.

Add the following code to the end of the file. Replace <TENANT_ID value> and <AAD_CLIENT_ID value> with the values for your Azure account and cluster.

services:
  nginx_ingress:
    version: 1.30.0-0.5.3
    chart_values:
      controller:
        kind: Deployment
        hostNetwork: false
        service:
          enabled: true
          type: LoadBalancer
        extraArgs:
          default-ssl-certificate: domino-platform/my-cert
  forge:
    version: 0.19.4
    install_timeout: 300
    chart_values:
      config:
        azure:
          tenantId: <TENANT_ID value>
          aadClientId: <AAD_CLIENT_ID value>

Note

Use fleetcommand-agent to install:

Run the fleetcommand-install.sh script from the same folder where the domino.yml file is located.

Note

Setup DNS:

Use kubectl -n domino-platform get svc nginx-ingress-controller to get the external IP to access your instance’s Domino management plane so that you can update your DNS records accordingly.

Validate your installation:

To perform basic validation, go to https://\<YOUR DOMAIN\>/auth/.
Login with the username keycloak and the password from the keycloak-http secret in the domino-platform namespace.

Use the following command to get the password:

echo -e "\nyour password is: $(kubectl get secret keycloak-http  -n domino-platform --template={{.data.password}} | base64 -d)\n"

Go to Users in the navigation pane and click Add User.
Enter the username, first name, last name, email address, and then click Save.
Go to the Credentials tab and add a password.
Optional: Disable Temporary.
Click Set Password.
Go to Role Mappings.
From Client Roles, select domino-play.
Select the User role and add it to your user.
Go to the main page for your Domino deployment (for example, https://\<YOUR DOMAIN\>) and sign in with your new Domino user.
Go to Environments > Domino Standard Environment Py3.8 R4.1 > Revisions and make sure the revision is active. If not, use Build Logs to try to solve the problem.
Go to Projects > Quick-start > Workspaces and launch a new workspace using Jupyter (this can take a while).
When the new workspace is created open main.ipynb and confirm that you can execute the script without errors.

Deploy Domino