Overview With Tanzu Kubernetes Grid, you can deploy Kubernetes clusters across software-defined datacenters (SDDC) and public cloud environments, including vSphere, Microsoft Azure, and Amazon EC2, providing organizations a consistent, upstream-compatible, regional Kubernetes substrate that is ready for end-user workloads and ecosystem integrations. In this post, I will explain the detailed steps to
TKG on Azure
TKG on Azure – Upgrade Management and workload clusters from 1.4.1 to 1.5.1
TKG 1.4 on Azure – Part 6 : Delete the clusters
This post covers the steps to delete the clusters that were deployed in TKG on Azure. Ensure to follow this doc only after double checking when NO APPLICATIONS ARE RUNNING. Cluster deletion completely wipes the pods running it. Delete workload cluster: Delete Management cluster: Management cluster deletion might usually take some time as
TKG 1.4 on Azure – Part 5 : Scaling operations
Scale management clusters: If you have deployed a development management cluster, like I did while creating i.e., with 1 control and worker nodes. You can scale the management clusters to production cluster type anytime using simple commands. In this post, I have covered manual scaling, but there is also auto scaling
TKG 1.4 on Azure – Part 4 : Deploy the application on workload cluster
TKG 1.4 on Azure – Part 3 : Create workload cluster
When you deploy Tanzu Kubernetes (workload) clusters to Microsoft Azure, you must specify options in the cluster configuration file to connect to your Azure account and identify the resources that the cluster will use. Create a yaml file with variables given in below template. for ex: wc-config.yaml Note: Below example is
TKG 1.4 on Azure – Part 2: Deploy management cluster
In this post, we will go through the steps to create management cluster through UI. Select Deploy under Microsoft Azure Fill in TENANT ID, CLIENT ID, CLIENT SECRET, SUBSCRIPTION ID that is collected in earlier post. Select the Region where you would like that management cluster to be deployed. Paste
