Installation prerequisites

You must complete certain tasks before you install HCL DevOps Velocity (Velocity) on Azure Kubernetes Service (AKS).

Note:

Installation of Velocity on AKS requires an internet connection to access the resources on AKS.

The following table lists the tasks that you must perform in sequence before you install Velocity. You can also find links for more information in the table.


S/N	Tasks	More information
1	Ensure that you have an active Azure subscription with sufficient permissions to create and manage AKS resources.	Azure Subscription Overview
2	Ensure that your account has Azure Kubernetes Service Cluster Admin, Owner, or Contributor permissions on the subscription or resource group.	AKS Access and Identity Options
3	Install and configure Azure CLI and authenticate to Azure.	Install Azure CLI
4	Create an Azure Kubernetes Service (AKS) cluster based on the system requirements.	Create an AKS Cluster
5	Open Azure Cloud Shell or use a local terminal with Azure CLI, kubectl and Helm configured.	Azure Cloud Shell Documentation
6	Create a node pool with three nodes within the AKS cluster based on the system requirements.	Add and Manage Node Pools in AKS
7	Create a namespace in the Kubernetes cluster where you install Velocity. `kubectl create namespace <custom_namespace_name>`	Kubernetes Namespaces Documentation
8	Install MongoDB depending on your environment and requirements. You should consider installing MongoDB on a standalone Azure Virtual Machine. This method avoids the complexity of managing Persistent Volume Claims (PVCs) and their reclaim policies in a Kubernetes cluster, which typically requires a skilled administrator. Alternatively, if you are installing within the Kubernetes cluster, you can deploy MongoDB as a StatefulSet. While this option is supported, the standalone VM setup is the better choice if you want to avoid the added complexity of container orchestration. MongoDB is not bundled with the Velocity installation package. Therefore, you must install MongoDB separately. As an alternative to self-managed deployments, you can also use MongoDB Atlas, a fully managed MongoDB service available on Azure. MongoDB Atlas eliminates the need to install, manage, and maintain MongoDB infrastructure while providing automated backups, monitoring, and scaling capabilities. If you use MongoDB Atlas, you must ensure that the outbound public IP address or IP addresses used by the AKS cluster are added to the MongoDB Atlas network access allowlist so that the Velocity application can connect to the MongoDB Atlas deployment.	MongoDB Documentation Bitnami MongoDB Helm Chart
9	Install an Ingress Controller on the Kubernetes cluster.	NGINX Ingress Controller for AKS
10	Ensure that you have an active domain name mapped to the ingress controller external IP address. You can create and manage DNS records using Azure DNS.	Azure DNS Documentation
11	Configure a custom SSL certificate.	Configuring a custom Secure Sockets Layer (SSL) certificate
12	Download the online or offline installation file and obtain the access key for Velocity.	Downloading the installation file