Create an Azure AKS Cluster - EcoSys - 2.0 - Installation & Upgrade - Hexagon PPM

EcoSys Connect Installation and Configuration (Azure Kubernetes Service)

Language
English (United States)
Product
EcoSys
Search by Category
Installation & Upgrade
EcoSys Version
2.0

Follow the steps below:

  1. Transfer the helm and install folders from the installation media to the installation machine.

  2. Go to the installer directory on the installer machine.

  3. To provide all the script executable permissions, run the command, ‘chmod +x *.sh

  4. Go to the aks sub directory

  5. To provide all the script executable permissions, run the command, ‘chmod +x *.sh’

  6. 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.

    Setting

    Description

    SUBSCRIPTION_NAME

    The name of the subscription being used in Azure. This will be used to lookup the subscription ID.

    CLUSTER_NAME

    The name of the cluster to be created. Default is connect-cluster

    RESOURCE_GROUP

    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

    REGION_NAME

    The Azure region the cluster/resource groups will be created in

    DEPLOYMENT_ID

    The deployment ID should be unique across all deployments because it is used to namespace components on shared infrastructure.

    Example: Production, Test, Project1-Production

    DEPLOYMENT_TARGET

    For deployments to Azure, set DEPLOYMENT_TARGET to DEPLOYMENT_TARGET_OPTION_AZURE

    PRODUCTION

    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.

    PRIVATE_INGRESS_IP

    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.

    SIZE

    Determines the # of nodes in the cluster. See Deployment sizing table for more information

    AKS_NODE_COUNT

    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

    AKS_NODE_VM_SIZE

    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.

    CONNECT_NAMESPACE

    The namespace used to install the Connect components

    AGENT_NAMESPACE

    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.

  7. Execute the login command in az cli to login to your subscription by running - ‘az login’-

    1. Complete the login process using credentials to access your Azure Subscription

  8. Create the cluster by running ‘./create-cluster.sh’

    1. The script prints the Service Principal information. Save this information for later use.

    2. 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.

  9. Install Istio into the cluster by running ‘./install-istio.sh’