When a cluster which has been provisioned by TMC, and therefore managed by TMC, has an available upgrade, you will see an “i” icon next to the version on the clusters UI view, hovering over this will tell you there is an upgrade ready.
Click the cluster name to take you into the cluster object to see the full details,
click the actions button
and select upgrade.
The Upgrade Cluster dialogue will appear. Select the version you want to upgrade to and click upgrade.
On both the Cluster list and Cluster Detailed view, the status will change to upgrading.
Once the upgrade has completed, the cluster will change back to ready and show the updated version.
Wrap-up and Resources
In this quick blog post, we used Tanzu Mission Control to upgrade a provisioned Tanzu Kubernetes Grid cluster which was running in AWS. All the steps provided in this blog post can be replicated using the TMC CLI as well.
As a reminder, to take real advantage of TMC I recommend you read the follow posts:
This blog post will cover a technical walk-through on using Tanzu Mission Control to deploy Tanzu Kubernetes clusters to AWS.
The follow up blog posts in this series are:
Tanzu Mission Control
- Getting Started with TMC
- - What is Tanzu Mission Control?
- - Creating a Cluster Group
- - Attaching a cluster to Tanzu Mission Control
- - Viewing your Cluster Objects
- - Where can I demo/test/trial this myself?
- Cluster Inspections
- - What Inspections are available
- - Performing Inspections
- - Viewing Inspections
- Workspaces and Policies
- - Creating a workspace
- - Creating a managed Namespace
- - Policy Driven Cluster Management
- - Creating Policies
- Using the Data Protection feature for backups and restores
- - Data Protection Overview
- - Create a AWS Data Protection Credential
- - Enable Data Protection on a Cluster
- - Running a backup manually or via an automatic schedule
- - Restoring your data
Using the AWS Hosted Management Cluster
In this example, we will use the default provided AWS Hosted Management cluster.
Alternatively, you can use the Tanzu CLI to provision a TKG Management cluster into AWS and attach this to Tanzu Mission Control.
Currently it is not supported to have a Management Cluster manage clusters across platforms.
I.e. Management Cluster in AWS that manages workload clusters in Azure.
To get started:
Go to Administration
Click the Management Clusters Tab
Click on the “aws-hosted” cluster object name
Create a provisioner
The default tab when selecting the “aws-hosted” management cluster object is the provisioner tab.
Click create provisioner
Provide a name for the provisioner
You will be taken back to your provisioner object which is created. Using the radio button to select the object will allow you to delete it. No other action is available.
Scroll to the bottom of the page, and select “Add/Upgrade”
Select the pak file for installation and follow the wizard.
Create a CSP API Token
For the vROPs management pack adapter to be able to communicate with TMC, we need an API token.
Log into https://console.cloud.vmware.com
Change to correct organisation that contains your TMC instance
Click your name in the top right hand corner and select “My Account”
Select the “API Tokens” tab, and then “Generate a new API Token” button.
Set your API Token name, expiry, and access control as required. Then click the generate button.
You will be shown a dialog box with your generated token. Save this in a safe space we will use it later on.
Connect vRealize Operations management pack adapter to Tanzu Mission Control
In vROPs UI go to Administration > Under Solutions, choose “Other Accounts” and click the “Add account” button.
From the account type list, choose Tanzu Mission Control.
Fill out the necessary details on the New Account screen.
For the credential click the + symbol, add in a name for the credential, and the CSP token you created earlier.
Select your newly created credential.
Select the validate button.
Hopefully you get a successful message.
You will see the account object in the Other Accounts view.
Auto-Discovering Tanzu Kubernetes Grid Clusters
Now you have your account added, whenever you provision a new cluster using Tanzu Mission Control, cAdvisor will be configured in the Kubernetes cluster and a Kubernetes account type will be created in vROps automatically for you.
Below I’ve created a cluster in AWS, and we can see the object has been created in vROPs.
And finally, here is my cluster showing in the one of the Kubernetes Dashboards.
This is a simple to implement feature but can make a massive difference in your ability to monitor your TKG clusters from the infrastructure view that vROPs provides. As your users create clusters via TMC, they don’t need to interact with the monitoring platform to ensure visibility.
In this blog post we will cover the following topics
- Data Protection Overview
- Create a AWS Data Protection Credential
- Enable Data Protection on a Cluster
- Running a backup manually or via an automatic schedule
- Restoring your data
The follow up blog posts are;
- Tanzu Mission Control
- - Getting Started with TMC
- - - What is Tanzu Mission Control?
- - - Creating a Cluster Group
- - - Attaching a cluster to Tanzu Mission Control
- - - Viewing your Cluster Objects
- - -Where can I demo/test/trial this myself?
- - Cluster Inspections
- - - What Inspections are available
- - - Performing Inspections
- - - Viewing Inspections
- - Workspaces and Policies
- - - Creating a workspace
- - - Creating a managed Namespace
- - - Policy Driven Cluster Management
- - - Creating Policies
TMC Data Protection Overview
Tanzu Mission Control implements data protection through the inclusion of the Project Velero, this tool is not enabled by default. This blog post will take you through the setup.
Data is stored externally to a AWS location, with volume backups remaining as part of the cluster where you’ve connected TMC.
Currently there is no ability to backup and restore data between Kubernetes clusters managed by TMC.
Create a AWS Data Protection Credential
First we need to create a AWS data protection credential, so that TMC can configure Velero within your cluster to save the data externally to AWS.
If you are looking for supported options for protecting data to other locations, I recommend you either look at deploying Project Velero manually outside of TMC (losing access to the data protection features in the UI) or look at another enterprise service such as Kasten.io.
On the Administration screen, click Accounts, and Create Account Credential.
Select > AWS data protection credential
Set your account name for easy identification and click to generate template and save this file to your machine.
The next steps will require configuration in the AWS console to create resources using CloudFormation so that Project Velero can export data to AWS. Here is the official VMware documentation on this configuration.
In the AWS Console, go to the CloudFormation service
Click to create a new stack
Click “Template is ready” as we will provide our template file from earlier.
Click to upload a template file
Select the file from your machine
Provide a stack name and click next
Ignore all the items on this page and click next
Review your configuration and click finish.
Once you’ve reviewed and clicked create/finish. You will be taken into the Stack itself.
You can click the Events tab and the refresh button to see the progress.