Install Release on Azure AKS Cluster

This section describes the procedure of fresh installation of the Release application on Azure AKS cluster using operator-based installer.

Intended Audience

This guide is intended for administrators with cluster administrator credentials who are responsible for application deployment.

Before You Begin

The following are the prerequisites required to migrate to the operator-based deployment:

  • Docker version 17.03 or later
  • The kubectl command-line tool
  • Access to a Kubernetes cluster version 1.17 or later
  • Kubernetes cluster configuration

Step 1—Create a folder for installation tasks

Create a folder on your workstation from where you will execute the installation tasks, for example, ReleaseInstallation.

Step 2—Download the Operator ZIP

  1. Download the file from the Deploy/Release Software Distribution site.
  2. Extract the ZIP file to the ReleaseInstallation folder.

Step 3—Update the Azure AKS Cluster Information

To deploy the Release application on the Kubernetes cluster, update the Infrastructure file parameters (infrastructure.yaml) in the location where you extracted the ZIP file with the parameters corresponding to the Azure AKS Kubernetes Cluster Configuration (kubeconfig) file as described in the table. You can find the Kubernetes cluster information in the default location ~/.kube/config.

Note: The deployment will not proceed further if the infrastructure.yaml is updated with wrong details.

Infrastructure File Parameters Azure AKS Kubernetes Cluster Configuration File Parameters Steps to Follow
apiServerURL server Enter the server details of the cluster.
caCert certificate-authority-data Before updating the parameter value, decode to base 64 format.
tlsCert client-certificate-data Before updating the parameter value, decode to base 64 format.
tlsPrivateKey client-key-data Before updating the parameter value, decode to base 64 format.

Step 4—Update the default Release Custom Resource Definitions.

  1. Run the following command to get the storage class list:

    kubectl get sc
  2. Run the keytool command below to generate the RepositoryKeystore:

    keytool -genseckey {-alias alias} {-keyalg keyalg} {-keysize keysize} [-keypass keypass] {-storetype storetype} {-keystore keystore} [-storepass storepass]


    keytool -genseckey -alias deployit-passsword-key -keyalg aes -keysize128 -keypass deployit -keystore /tmp/repository-keystore.jceks -storetype jceks -storepass test123
  3. Convert the Release license and the repository keystore files to the base64 format:

    • To convert the xlrLicense into base64 format, run:

      cat <License.lic> | base64 -w 0
    • To convert RepositoryKeystore to base64 format, run:

      cat <repository-keystore.jceks> | base64 -w 0

    Note: The above commands are for Linux-based systems. For Windows, there is no built-in command to directly perform Base64 encoding and decoding. However, you can use the built-in command certutil -encode/-decode to indirectly perform Base64 encoding and decoding.

  4. Update the mandatory parameters as described in the following table:

    Note: For deployments on test environments, you can use most of the parameters with their default values in the dairelease_cr.yaml file.

    Parameter Description
    KeystorePassphrase The passphrase for the RepositoryKeystore.
    Persistence.StorageClass The storage class that must be defined as Azure AKS cluster.
    RepositoryKeystore Convert the repository keystore file for Release to the base64 format.
    ingress.hosts DNS name for accessing UI of Release.
    postgresql.persistence.storageClass Storage Class to be defined as PostgreSQL.
    rabbitmq.persistence.storageClass Storage Class to be defined as RabbitMQ.
    xlrLicense Release license

    Note: For deployments on production environments, you must configure all the parameters required for your Azure AKS AKS production setup in the dairelease_cr.yaml file. The table in Step 4.5 lists these parameters and their default values, which can be overridden as per your setup requirements and workload. You can override the default parameters, and specify the parameter values.

  5. Update the default parameters as described in the following table:

    Note: The following table describes the default parameters in the dairelease_cr.yaml file. If you want to use your own database and messaging queue, refer Using Existing DB and Using Existing MQ topics, and update the dairelease_cr.yaml file. For information on how to configure SSL/TLS with Release, see Configuring SSL/TLS.

Description Default
K8sSetup.Platform The platform on which you install the chart. Allowed values are PlainK8s and AzureAKS AWSEKS
replicaCount Number of replicas 3
ImageRepository Image name xebialabs/xl-release
ImageTag Image tag 10.2
ImagePullPolicy Image pull policy, Defaults to Always if image tag is ’latest’,set to IfNotPresent Always
ImagePullSecret Specifies docker-registry secret names. Secrets must be manually created in the namespace NA
haproxy-ingress.install Install haproxy subchart. If you have haproxy already installed, set install to false TRUE
haproxy-ingress.controller.kind Type of deployment, DaemonSet or Deployment DaemonSet
haproxy-ingress.controller.service.type Kubernetes Service type for haproxy. It can be changed to LoadBalancer or NodePort NodePort
ingress.Enabled Exposes HTTP and HTTPS routes from outside the cluster to services within the cluster TRUE
ingress.annotations Annotations for ingress controller
/ option httpchk GET
/ha/health HTTP/1.0
ingress.path You can route an Ingress to different Services based on the path /xl-release/
ingress.tls.secretName Secret file that contains the tls private key and certificate example-secretsName
ingress.tls.hosts DNS name for accessing ui of Release using tls. See configuring TLS SSL
AdminPassword Admin password for xl-release If user does not provide password, random 10 character alphanumeric string will be generated
resources CPU/Memory resource requests/limits. User can change the parameter accordingly NA
postgresql.install postgresql chart with single instance. Install postgresql chart. If you have an existing database deployment, set install to false. TRUE
postgresql.postgresqlUsername PostgreSQL user (creates a non-admin user when postgresqlUsername is not postgres) postgres
postgresql.postgresqlPassword PostgreSQL user password random 10 character alphanumeric string
postgresql.replication.enabled Enable replication FALSE
postgresql.postgresqlExtendedConf.listenAddresses Specifies the TCP/IP address(es) on which the server is to listen for connections from client applications *
postgresql.postgresqlExtendedConf.maxConnections Maximum total connections 500
postgresql.initdbScriptsSecret Secret with initdb scripts contain sensitive information
Note: This parameter can be used with initdbScriptsConfigMap or initdbScripts. The value is evaluated as a template.
postgresql.service.port PostgreSQL port 5432
postgresql.persistence.enabled Enable persistence using PVC TRUE
postgresql.persistence.size PVC Storage Request for PostgreSQL volume 50Gi
postgresql.persistence.existingClaim Provide an existing PersistentVolumeClaim, the value is evaluated as a template. NA
postgresql.resources.requests CPU/Memory resource requests requests: memory: 1Gi memory: cpu: 250m
postgresql.resources.limits Limits limits: memory: 2Gi, limits: cpu: 1
postgresql.nodeSelector Node labels for pod assignment {}
postgresql.affinity Affinity labels for pod assignment {}
postgresql.tolerations Toleration labels for pod assignment []
UseExistingDB.Enabled If you want to use an existing database, change postgresql.install to false. FALSE
UseExistingDB.XLR_DB_URL Database URL for xl-release NA
UseExistingDB.XLR_DB_USERNAME Database User for xl-release NA
UseExistingDB.XLR_DB_PASSWORD Database Password for xl- NA
UseExistingDB.XLR_REPORT_DB_URL Database URL for xlr_report NA
UseExistingDB.XLR_REPORT_DB_USER Database User for xlr_report NA
UseExistingDB.XLR_REPORT_DB_PASS Database Password for xlr_report NA
rabbitmq.install Install rabbitmq chart. If you have an existing message queue deployment, set install to false. TRUE
rabbitmq.rabbitmqUsername RabbitMQ application username guest
rabbitmq.rabbitmqPassword RabbitMQ application password random 24 character long alphanumeric string
rabbitmq.rabbitmqErlangCookie Erlang cookie RELEASERABBITMQCLUSTER
rabbitmq.rabbitmqMemoryHighWatermark Memory high watermark 500MB
rabbitmq.rabbitmqNodePort Node port 5672
rabbitmq.extraPlugins Additional plugins to add to the default configmap rabbitmq_shovel,rabbitmq_shovel_management,rabbitmq_federation,rabbitmq_federation_management,rabbitmq_amqp1_0,rabbitmq_management
rabbitmq.replicaCount Number of replicas 3
rabbitmq.rbac.create If true, create & use RBAC resources TRUE
rabbitmq.service.type Type of service to create ClusterIP
rabbitmq.persistentVolume.enabled If set to True, persistent volume claims are created TRUE
rabbitmq.persistentVolume.size Persistent volume size 20Gi
rabbitmq.persistentVolume.annotations Persistent volume annotations {}
rabbitmq.persistentVolume.resources Persistent Volume resources {}
rabbitmq.persistentVolume.requests CPU/Memory resource requests requests:
memory: 250Mi memory: cpu: 100m
rabbitmq.persistentVolume.limits Limits limits:
memory: 550Mi, limits: cpu: 200m
rabbitmq.definitions.policies HA policies to add to definitions.json {”name”:
/,definition: {ha-mode: all,ha-sync-mode:
automatic, ha-sync-batch-size`: 1}}
rabbitmq-ha.definitions.globalParameters Pre-configured global parameters {name:
cluster_name,value: }
rabbitmq-ha.prometheus.operator.enabled Enabling Prometheus Operator FALSE
UseExistingMQ.Enabled If you want to use an existing Message Queue change rabbitmq-ha.instal to false FALSE
UseExistingMQ.XLR_T\ASK_QUEUE_USERNAME Username for xl-task queue NA
UseExistingMQ.XLR_TASK_QUEUE_PASSWORD Password for xl-task queue NA
UseExistingMQ.XLR_TASK_QUEUE_NAME Name for xl-task queue NA
HealthProbes Would you like a HealthProbes to be enabled? TRUE
HealthProbesLivenessTimeout Delay before liveness probe is initiated 90
HealthProbesReadinessTimeout Delay before readiness probe is initiated 90
HealthProbeFailureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded 12
HealthPeriodScans How often to perform the probe 10
nodeSelector Node labels for pod assignment {}
tolerations Toleration labels for pod assignment []
affinity Affinity labels for pod assignment {}
Persistence.Enabled Enable persistence using PVC true
Persistence.Annotations Annotations for the PVC {}
Persistence.AccessMode PVC Access Mode for volume ReadWriteOnce
Persistence.Size XLR PVC Storage Request for volume. For production grade setup, size must be changed 5Gi

Step 5—Download and set up the XL CLI

  1. Download the XL-CLI binaries.


    Note: For $VERSION, substitute with the version that matches your product version in the public folder.

  2. Enable execute permissions.

    chmod +x xl
  3. Copy the XL binary in a directory that is on your PATH.

    echo $PATH


    cp xl /usr/local/bin
  4. Verify the release version.

    xl version

Step 6—Set up the XL Deploy container instance

  1. Run the following command to download and start the Deploy instance:

    docker run -d -e "ADMIN_PASSWORD=admin" -e "ACCEPT_EULA=Y" -p 4516:4516 --name xld xebialabs/xl-deploy:10.2
  2. To access the Deploy interface, go to:
    http://<host IP address>:4516/

Step 7—Activate the deployment process

Go to the root of the extracted file and run the following command:

xl apply -v -f digital-ai.yaml

Step 8—Verify the deployment status

  1. Check the deployment job completion using XL CLI.
    The deployment job starts the execution of various tasks as defined in the digital-ai.yaml file in a sequential manner. If you encounter an execution error while running the scripts, the system displays error messages. The average time to complete the job is around 10 minutes.

Note: The running time depends on the environment.

Deployment Status

To troubleshoot runtime errors, see Troubleshooting Operator Based Installer.

Step 9—Verify if the deployment was successful

To verify the deployment succeeded, do one of the following:

  • Open the local Deploy application, go to the Explorer tab, and from Library, click Monitoring > Deployment tasks
Successful Release Deployment
  • Run the following command in a terminal or command prompt:

Deployment Status Using CLI Command

Step 10—Perform sanity checks

Open the Release application and perform the required sanity checks.