Setting up the Resource Group

After you login to the Azure portal, follow these steps to set up a Resource Group. A resource group is an area for all your AKS resources such as Network Security Group, Virtual Network, Storage account (used to deploy helm charts), Container Registry (where the TDV image is stored) and a Kubernetes Cluster.

Creating a Container Registry

Choose your Resource Group.

Click on the "Create" button from your Resource Group Page.

Choose Container Registry.

In the New Container Registry dialog, choose the default settings for Basics, Networking, encryption and Tags. Finally. review the chosen options and click on Create to create your Container Registry.

Once the Container Registry is created, push your TDV images to this location. Refer to the chapter TDV Docker Container for more information on how to build your TDV image and push it to the registry. You may also refer to the following Azure documentation for more details about how to push an image to a container registry.

https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-prepare-acr?tabs=azure-cli

Creating a Cluster

Follow these steps to create a Kubernetes cluster in your resource group:

From your Resource Group, click on Create and choose the option Kubernetes Service to create a Kubernetes Cluster.
Choose your subscription and your resource group if it is not selected already.
Provide a name for your Kubernetes cluster.
Choose a region that is appropriate for your organization.
Choose a Kubernetes version. Currently TDV supports version 1.21.0 or a higher version in 1.21.X.
Use the defaults for the worker node settings such as Node size, Scale method and Node count range.
Use the default settings for the rest of the Kubernetes Create Cluster dialogue - Node pools, Authentication, Tags.
In the Networking tab, choose your Container Registry. Refer to the section Creating a Container Registry for more information on creating a registry.
Finally click on Create to create the cluster.

Deploying the TDV Helm Chart

The TDV Helm chart provisions the necessary storage for the TDV application on the Kubernetes Cluster. TIBCO Data Virtualization Container distribution includes the helm chart with certain default settings. You can run the helm chart using a pre-built script provided.

You can use an Azure CLI or a Cloud-shell to connect to Azure and execute administrative commands on the Azure resources. These tools allow the execution of commands through interactive command-line prompts or a script. Refer to the following documentation on the Azure CLI and Azure Cloud Shell for more information about using these tools:

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli

https://docs.microsoft.com/en-us/azure/cloud-shell/overview

To edit/run the helm chart and scripts using one of these tools:

Open the Cloud Shell interface or the Azure CLI.
Connect to your cluster:

—

Click on the option Connect in the top menu bar of the Cluster. A window is displayed with all the connection details and the associated kubernetes commands to use in your shell.

—

Use the commands in your shell interface to connect to the cluster. (for example, run these commands:

$ az account set --subscription <subscription id>

$ az aks get credentials --resource-group <resource group name> --name <user id>

—

Once the connection to cluster is established, you can then issue any kubernetes command.

For example, to get information on all the pods running, type the following command:

$ kubectl get pods --all-namespaces

Upload your TDV Helm charts archive file (i.e. TIB_tdv_<version>_helmchart.tar.gz) to Azure using the Upload option in your Cloud shell. If you are using the Azure CLI, make sure that has access to the files extracted from the TIB_tdv_<version>_helmchart.tar.gz.

Once you have connected to the cluster and have all the files you need, you can use the TDV scripts to install your helm chart. Refer to the section Configuring Kubernetes Using Quick Start Script.

Azure AKS uses a load balancer service to route all client requests across all your TDV applications that are ready to fulfill those requests. Azure AKS will automatically assign an external IP for your TDV service endpoint. To get the external IP of that load balancer service run:

$ kubectl get svc -o wide -n tdv

Note: If you also deployed the TDV HAProxy application, then you will see two TDV services with external IPs. One is for the Client External IP and one for the Monitor External IP (Refer to the illustration ClusterTDV Deployment Mode: for the Cluster TDV Deployment Mode architecture).

The screen below is a sample output of the Azure Cloud Shell displaying the load balancer service and the IP to access.