This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

After deployment, you can reconfigure your your Tanzu Kubernetes Grid Integrated Edition installation in VMware Tanzu Kubernetes Grid Integrated Edition Management Console, either by using the wizard or by importing an updated YAML file.

Reconfigure Your Tanzu Kubernetes Grid Integrated Edition Deployment in the Wizard

The procedure to reconfigure Tanzu Kubernetes Grid Integrated Edition deployments in the wizard is as follows.

  1. Expand Configuration and go to the TKGI Configuration view of the management console.
  2. Select Wizard to be taken to the configuration wizard for Tanzu Kubernetes Grid Integrated Edition.

    Reconfigure your Tanzu Kubernetes Grid Integrated Edition deployment View a larger version of this image

  3. Expand the different sections of the wizard and change the configurations as necessary.

    For information about which configuration options you can change, see Which Options Can I Reconfigure? below.

    For the options that you can modify, refer to Deploy Tanzu Kubernetes Grid Integrated Edition by Using the Configuration Wizard for instructions about how to fill in each section.
  4. When you have finished reconfiguring, click Generate Configuration.
  5. Optionally export the PksConfiguration.yaml file to save a copy of your configuration.
  6. Click Apply Configuration and Continue to complete the reconfiguration of Tanzu Kubernetes Grid Integrated Edition.

Reconfigure Your Tanzu Kubernetes Grid Integrated Edition Deployment by Importing a YAML File

The procedure to reconfigure Tanzu Kubernetes Grid Integrated Edition deployments by importing an updated YAML file is as follows.

  1. Expand Configuration and go to the TKGI Configuration view of the management console.
  2. Select Wizard to be taken to the configuration wizard for Tanzu Kubernetes Grid Integrated Edition.
  3. Scroll to the bottom of the screen and click Import YAML.

    Reconfigure your Tanzu Kubernetes Grid Integrated Edition deployment

  4. Drag the YAML file into the Import Configuration File window, or click Browse to navigate to it.
  5. In the Configuration File editor, modify the contents of the YAML file appropriately for the new instance of Tanzu Kubernetes Grid Integrated Edition that you want to deploy.

    For information about which configuration options you can change, see Which Options Can I Reconfigure? below.

    If the YAML was generated by an instance of the management console that is running in a different vSphere environment, update the passwords for NSX Manager, vCenter Server, and Harbor. For more information see Deploy Tanzu Kubernetes Grid Integrated Edition by Importing a YAML Configuration File.

    To abandon this YAML and start again, click Import to upload the YAML again or to import a new one.

    You can also click the Edit in Wizard button, to open the imported configuration in the wizard.
  6. Click Apply Configuration and Continue to complete the reconfiguration of Tanzu Kubernetes Grid Integrated Edition.

Which Options Can I Reconfigure?

After the initial deployment of Tanzu Kubernetes Grid Integrated Edition, there are certain options that you cannot reconfigure. In particular, you cannot make significant infrastructure changes.

The table below lists what you can and cannot modify on an existing Tanzu Kubernetes Grid Integrated Edition deployment.

Section Cannot Modify Can Modify
vCenter Account
  • vCenter Server instance
  • Datacenter
  • Username
  • Password
  • vCenter Server address, if it changes
Networking: Container Networking Interface You cannot change between NSX-T Data Center (Automated NAT Deployment), NSX-T Data Center (Bring Your Own Topology), and vSphere without NSX-T. None.
Networking: NSX Manager Details You cannot change the deployment to a different NSX Manager instance.
  • Username
  • Password
  • NSX Manager address, if it changes
  • NSX Manager CA Cert*
Networking: NSX-T Data Center (Automated NAT Deployment)
  • Tier0 Active-Active Mode
  • Deployment CIDR
  • Deployment Network Reserved IP Range
  • Usable Range of Floating IPs
All other options.
Networking: NSX-T Data Center (Bring Your Own Topology)
  • Network for TKGI Management Plane
  • Floating IP Pool ID
  • Deployment Network Reserved IP Range
  • NAT mode
All other options.
Networking: vSphere Without NSX-T
  • Deployment Network Reserved IP Range
  • Service Network Reserved IP Range
All other options.
Identity None. All options**.
Availability Zones
  • Management availability zone
All other options, including adding and deleting availability zones.
Plans None. All options, including adding and deleting plans.
Integrations None. All options.
Harbor
  • Harbor FQDN
  • Authentication mode
All other options.
CEIP and Telemetry None. All options.

* If you update the NSX Manager CA Cert field, TKGI MC will update BOSH and TKGI to the new NSX-T CA certificate. For clusters that you have already created, you must update those clusters to use the new certificate. You must manually update the NSX-T CA certificate for the related NCP configurations.
** If you previously used a local user database and change to AD/LDAP or SAML, the local user database is deleted.

check-circle-line exclamation-circle-line close-line
Scroll to top icon