Follow the steps below:
Transfer the helm and install folders from the installation media to the installation machine.
Go to the installer directory on the installer machine.
To provide all the script executable permissions, run the command, ‘chmod +x *.sh
Go to the aks sub directory
To provide all the script executable permissions, run the command, ‘chmod +x *.sh’
Edit the env.sh file and customize any settings based on your infrastructure.
The following are few important settings to adjust.
It is recommended to only change the property settings in the env.sh script. Modifying the code in env.sh script or any other script is not recommended.
The name of the subscription being used in Azure. This will be used to lookup the subscription ID.
The name of the cluster to be created. Default is connect-cluster
The name of the resource group to be used. By default set to use the name from CLUSTER_NAME.
If the resource group does not exist, the script will create it
The Azure region the cluster/resource groups will be created in
The deployment ID should be unique across all deployments because it is used to namespace components on shared infrastructure.
Example: Production, Test, Project1-Production
For deployments to Azure, set DEPLOYMENT_TARGET to DEPLOYMENT_TARGET_OPTION_AZURE
Set to true or false. Determine the deployment mode which influences the deployment size and CPU/memory settings. See Deployment Sizing table for more information.
By default, an Istio Gateway will be installed into the cluster and configured to get a public IP address. If you change PRIVATE_INGRESS_IP to true, the gateway configuration will be updated to get a private (non public) IP.
Determines the # of nodes in the cluster. See Deployment sizing table for more information
This setting and the following code setting AKS_NODE_COUNT are used in the env.sh are used to determine the # of nodes in the deployment. This should not be changed, the number of nodes will be determined automatically based on the PRODUCTION and SIZE settings. See Deployment sizing table for more information
The Node VM family is used when creating the node pool in the cluster. The deployment requires Standard_F4s_v2 and it is not recommended to change this setting.
The namespace used to install the Connect components
The namespace used to install the Agent components
There are other settings and statements in the env.sh file. It is not recommended to change these settings without consulting Hexagon support.
Execute the login command in az cli to login to your subscription by running - ‘az login’-
Complete the login process using credentials to access your Azure Subscription
Create the cluster by running ‘./create-cluster.sh’
The script prints the Service Principal information. Save this information for later use.
Check the Control plane and Node Pool Kubernetes versions and ensure they meet the required minimum versions. If not, upgrade both to meet the required minimum versions.
Install Istio into the cluster by running ‘./install-istio.sh’