To upgrade an existing installation of Tanzu Kubernetes Grid Integrated Edition Management Console, you download and deploy a new version of the Tanzu Kubernetes Grid Integrated Edition Management Console VM. You then use the management console UI of the new version to migrate the configuration of the old installation to the new one.
You can only use the management console to upgrade an Tanzu Kubernetes Grid Integrated Edition installation that was deployed from a previous version of the management console. You cannot use the console to upgrade an instance of Tanzu Kubernetes Grid Integrated Edition that you installed manually.
WARNING: Do not select Power Off.
Follow the instructions in Deploy the Tanzu Kubernetes Grid Integrated Edition Management Console to deploy and power on the new version of the management console VM from the new OVA template.
Notes: If you want to reuse the same IP address as before, and you assigned a temporary IP address to the old version of the management console, configure the network settings of the new Management Console to use the same static IP address as previously.
If you used custom certificates when you deployed the previous version of the management console, you must use the same certificates when you deploy the new version of the management console. If you do not provide the certificate details when you deploy the new version, self-signed certificates are generated.
When the OVA deployment has completed successfully, you can access the new version of the management console.
root
and the root password that you set when you deployed the new version of the OVA template.Tanzu Kubernetes Grid Integrated Edition Management Console provides an upgrade wizard to help you to migrate the configuration of your old deployment to the new version.
To get help in the wizard at any time, click the ? icon at the top of the page, or click the More Info… links in each section to see help topics relevant to that section. Click the i icons for tips about how to fill in specific fields.
If any sections of the configuration wizard are marked in red, expand and reconfigure them.
Sections might appear in red because they are in an error state, or because they relate to new configuration parameters that were not present in the previous version. For information about how to configure each section, see Deploy Tanzu Kubernetes Grid Integrated Edition by Using the Configuration Wizard. For information about new parameters that have been added, see the release notes for the version to which you are upgrading.
WARNING: You cannot change the Ops Manager FQDN of Tanzu Kubernetes Grid Integrated Edition once it has already deployed.
To specify an FQDN address for the Ops Manager VM, update the YAML as follows:opsman_fqdn:
entry in the YAML file.opsman_fqdn:
entry with the Ops Manager VM FQDN: opsman_fqdn: "myopsman.example.com"
PksConfiguration.yaml
.You can now access the upgraded Tanzu Kubernetes Grid Integrated Edition control plane and continue deploying Kubernetes clusters. Any new clusters that you deploy from the upgraded Tanzu Kubernetes Grid Integrated Edition control plane will use the new version of Kubernetes.
Important: Existing clusters are not upgraded during the upgrade of Tanzu Kubernetes Grid Integrated Edition Management Console. You must manually upgrade any existing clusters.
For information about how you can use Tanzu Kubernetes Grid Integrated Edition Management Console to monitor and manage your upgraded deployment, see Monitor and Manage Tanzu Kubernetes Grid Integrated Edition in the Management Console.
You can decommission the old version of Tanzu Kubernetes Grid Integrated Edition by deleting the previous version of the Tanzu Kubernetes Grid Integrated Edition Management Console VM from the vSphere inventory.