Release Notes

Page last updated:

This topic contains release notes for Tanzu Kubernetes Grid Integrated Edition (TKGI) v1.12.

Warning: Before installing or upgrading to Tanzu Kubernetes Grid Integrated Edition v1.12, review the Breaking Changes below.

TKGI v1.12.0

Release Date: September 09, 2021

Product Snapshot

* Components marked with an asterisk have been updated.
** To use PodSecurityPolicy features, you must use Ops Manager v2.10.17 or later. Do not use TKGI with Ops Manager v2.10.17 with vSphere CPIv2. For more information, see v2.10.17 in Ops Manager v2.10 Release Notes.
*** To use Policy API features, you must use NSX-T v3.1.3.

Upgrade Path

The supported upgrade paths to TKGI v1.12.0 are from Tanzu Kubernetes Grid Integrated Edition v1.11.0 and later.

Features

TKGI v1.12.0 has the following features and enhancements:

Supports NSX-T Policy API

(Beta) Supports NSX-T Policy API for new installations. See Considerations for Using the NSX-T Policy API with TKGI and Networking in Installing Tanzu Kubernetes Grid Integrated Edition on vSphere with NSX-T.

Warning: Support for the NSX-T Policy API is currently in beta and is intended for evaluation and test purposes only. Do not use this feature in a production environment.

Supports Cluster Cert Rotation Using the CLI

Supports Kubernetes cluster certificate rotation using the TKGI CLI. See Rotate Kubernetes Cluster Certificates.

Supports Persistent Redirect URIs

Supports assigning persistent UAA cluster_client redirect_uri URIs to clusters on the TKGI tile. UAA redirect URIs configured on the TKGI tile persist through cluster updates and TKGI upgrades. For more information on configuring persistent UAA redirect URIs, see UAA in Installing TKGI.

Supports Clusters That Use the containerd Runtime

Supports creating and managing clusters that use the containerd runtime. Newly created clusters use the containerd runtime by default. You can optionally create clusters that use a docker runtime. For more information, see Creating Clusters.

Note: You cannot manually change the container runtime for existing clusters. TKGI does not automatically update existing clusters to use the containerd runtime.

Configure Clusters to Use NSX-T Client-Side ssl Profiles

Supports using Network Profiles to configure a cluster to use an NSX-T client-side ssl profile. For information about using a Network Profile to configure a cluster to use an NSX-T client-side ssl profile, see Network Profile Parameters or Confirm the Network Profile Property Supports Updates in Creating and Deleting Network Profiles (NSX-T Only).

Configure Clusters to Use NSX-T Load Balancer TCP Multiplexing

Supports using Network Profiles to configure a cluster to use NSX-T load balancer TCP multiplexing and to limit the number of allowed TCP multiplexing connections. For information about using a Network Profile to configure a cluster to use NSX-T load balancer TCP multiplexing, see Network Profile Parameters or Confirm the Network Profile Property Supports Updates in Creating and Deleting Network Profiles (NSX-T Only).

Migrate from VCP to the Automatically Installed vSphere CSI Driver

Supports migrating an existing Linux cluster from VCP to the automatically installed vSphere CSI Driver. For more information about migrating existing clusters to the vSphere CSI Driver, see Migrate from VCP to the Automatically Installed vSphere CSI Driver in Deploying and Managing Cloud Native Storage (CNS) on vSphere.

SAML IdP Enhancements

Includes the following SAML IdP enhancements:

• Supports users directly authenticating with the configured external identity provider.
  
• Supports automatically bypassing the scope approval screen for the tkgi get-credentials CLI command and when logging in to the TKGI CLI.
  

Supports Securing Log Forwarding with a Custom CA Certificate

Supports optionally securing syslog ClusterLogSink and LogSink log forwarding with a custom CA certificate. For more information, see Create a Syslog ClusterLogSink or LogSink Resource.

Additional Features

TKGI v1.12.0 includes the following additional features:

• Supports configuring the MetricSink telegraf interval setting. For more information, see Create a ClusterMetricSink or MetricSink Resource in Creating and Managing Sink Resources.
  
• Supports NetApp Trident without manually sharing the root filesystem on each worker node. For more information about Trident, see Trident for Kubernetes in the NetApp documentation.
  
• Supports using logsink to forward logs with TLS enabled in addition to the existing support for forwarding logs with TLS disabled.
  

Resolved Issues

TKGI v1.12.0 has the following resolved issues:

• Fixes Tags Applied Using tkgi cli Commands Are Removed during tkgi update-cluster.
  
• Fixes Unexplained Errors After Interrupting a Log Stream When Using Antrea Networking.
  
• Fixes Kubernetes Pods on NSX-T Become Stuck in a Creating State.
  
• Fixes You Cannot Use vRealize Log Insight to Monitor NCP.
  
• Fixes CA Certificates Initially Created by Ops Manager v1.8.3 and Earlier Are Not Supported.
  
• Fixes Fluent Bit ClusterLogSink Returns ‘TCP Connection Failed’ While CEIP Telemetry Services Are Disabled.
  
• Fixes “drain-cluster-windows” Errand Does Not Exist.
  
• Fixes 'Invalid Gateway for Network’ Error after Updating a Cluster with Both nodes_dns And IP Subnet Range Parameters.
  
• Fixes Cluster Fails to Restart.
  
• Fixes Wavefront Collector is Duplicated or Not Collecting from TKGI Namespaces.
  
• Fixes The TKGI API VM fluentd.stdout.log Grows While vRealize Log Insight is Disabled.
  
• Fixes Windows Workloads With Attached Dynamic PVs Must Be Removed before Deleting a Cluster.
  
• Fixes Nodes with More Than 30 Stateful Pods Are in a NotReady State.
  
• Fixes Telegraf Agent Unable to Read From localhost Port 8080.
  
• Fixes Node Hostnames Are Not Resolved for BYO DNS in Azure Environments.
  
• The observability-manager ClusterRole and the metric-controller ClusterRole now use the observability-manager and metric-controller PodSecurityPolicy (PSP) instead of using the pks-priviledged PSP.
• Supports CA certificates containing subject and issuer fields.
  

Deprecations

The following TKGI features have been deprecated or removed from TKGI v1.12:

• Support for DenyEscalatingExec has been removed from Kubernetes v1.21 and can no longer be configured in the TKGI tile. For more information, see DenyEscalatingExec in the Kubernetes documentation.
  

Upcoming Deprecations

The following TKGI features will be deprecated or removed in future versions of TKGI:

• Flannel Support: Support for the Flannel Container Networking Interface (CNI) will be deprecated in TKGI v1.13. VMware recommends that you upgrade your Flannel CNI-configured clusters to the Antrea CNI. For more information about Flannel CNI deprecation, see About Upgrading from the Flannel CNI to the Antrea CNI in About Tanzu Kubernetes Grid Integrated Edition Upgrades.

• Docker Support: kubelet support for Docker images has been deprecated and Docker support will be completely removed in Kubernetes v1.24. TKGI v1.12 and later support containerd images.

• VCP Support: VCP support has been deprecated and support will be completely removed in a future TKGI version.

Known Issues

TKGI v1.12.0 has the following known issues:

Warning: Do not use TKGI with Ops Manager v2.10.17 with vSphere CPIv2. For more information, see v2.10.17 in Ops Manager v2.10 Release Notes.

TKGI MC Unable to Manage TKGI after Restoring the TKGI Control Plane from Backup

Symptom

After you restore Ops Manager and the TKGI API VM from backup, TKGI functions normally, but your TKGI MC tabs include the following error: “…product ‘pivotal-container service’ is not deployed…”.

Explanation

TKGI MC is associated with an Ops Manager with a specific name. If you rename Ops Manager with a new name while restoring, your TKGI MC will not recognize the restored Ops Manager and cannot manage it.

Kubernetes Pods on NSX-T Become Stuck in a Creating State

Symptom

The pods in your TKGI Kubernetes clusters on NSX-T become stuck in a creating state. The connections between nsx-node-agent and hyperbus repeatedly close, log Couldn't connect to 'tcp://...' (error: 111-Connection refused), and have a status of COMMUNICATION_ERROR.

Explanation

For information and workaround steps for this Known Issue, see Issue 2795268: Connection between nsx-node-agent and hyperbus flips and Kubernetes pod is stuck at creating state in NSX Container Plugin 3.1.2 Release Notes in the VMware documentation.

Pods Stop After Upgrading From NSX-T v3.0.2 to v3.1.0 on vSphere 7.0 and 7.0.1

Symptom

Your TKGI-provisioned Pods stop after upgrading from NSX-T v3.0.2 to NSX-T v3.1.0 on vSphere 7.0 and 7.0.1.

Explanation

For information, see Issue 2603550: Some VMs are vMotioned and lose network connectivity during UA nodes upgrade in the VMware NSX-T Data Center 3.1.1 Release Notes.

Workaround

To avoid the loss of network connectivity during UA node upgrade, ensure DRS is set to manual mode during your upgrade from NSX-T v3.0.2 to v3.1.0.

If you upgraded to NSX-T v3.1.0 with DRS in automation mode, run the following on the affected Pods’ master VMs to restore Pod connectivity:

monit restart ncp

For more information about upgrading NSX-T v3.0.2 to NSX-T v3.1.0, see Upgrade NSX-T Data Center to v3.0 or v3.1.

Error: Could Not Execute “Apply-Changes” in Azure Environment

Symptom

After clicking Apply Changes on the TKGI tile in an Azure environment, you experience an error ’…could not execute “apply-changes”…’ with either of the following descriptions:

• {“errors”:{“base”:[“undefined method 'location’ for nil:NilClass”]}}
• FailedError.new(“Resource Groups in region ’#{location}’ do not support Availability Zones”))

For example:

INFO | 2020-09-21 03:46:49 +0000 | Vessel::Workflows::Installer#run | Install product (apply changes)
2020/09/21 03:47:02 could not execute "apply-changes": installation failed to trigger: request failed: unexpected response from /api/v0/installations:
HTTP/1.1 500 Internal Server Error
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Mon, 21 Sep 2020 17:51:50 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: f5fc99c1-21a7-45c3-7f39
X-Runtime: 9.905591
X-Xss-Protection: 1; mode=block

44
{"errors":{"base":["undefined method `location' for nil:NilClass"]}}
0

Explanation

The Azure CPI endpoint used by Ops Manager has been changed and your installed version of Ops Manager is not compatible with the new endpoint.

Workaround

Run the following Ops Manager CLI command:

om --skip-ssl-validation --username USERNAME --password PASSWORD --target https://OPSMAN-API curl --silent --path /api/v0/staged/director/verifiers/install_time/IaasConfigurationVerifier -x PUT -d '{ "enabled": false }'

Where:

• USERNAME is the account to use to run Ops Manager API commands.
• PASSWORD is the password for the account.
• OPSMAN-API is the IP address for the Ops Manager API

For more information, see Error 'undefined method location’ is received when running Apply Change on Azure in the VMware Tanzu Knowledge Base.

VMware vRealize Operations Does Not Support Windows Worker-Based Kubernetes Clusters

VMware vRealize Operations (vROPs) does not support Windows worker-based Kubernetes clusters and cannot be used to manage TKGI-provisioned Windows workers.

TKGI Wavefront Requires Manual Installation for Windows Workers

To monitor Windows-based worker node clusters with a Wavefront collector and proxy, you must first install Wavefront on the clusters manually, using Helm. For instructions, see the Wavefront section of the Monitoring Windows Worker Clusters and Nodes topic.

Pinging Windows Worker Kubernetes Clusters Does Not Work

TKGI-provisioned Windows worker-based Kubernetes clusters inherit a Kubernetes limitation that prevents outbound ICMP communication from workers. As a result, pinging Windows workers does not work.

For information about this limitation, see Limitations > Networking in the Windows in Kubernetes documentation.

Velero Does Not Support Backing Up Stateful Windows Workloads

You can use Velero to back up stateless TKGI-provisioned Windows workers only. You cannot use Velero to back up stateful Windows applications. For more information, see Velero on Windows in Basic Install in the Velero documentation.

Tanzu Mission Control Integration Not Supported on GCP

TKGI on Google Cloud Platform (GCP) does not support Tanzu Mission Control (TMC) integration, which is configured in the Tanzu Kubernetes Grid Integrated Edition tile > the Tanzu Mission Control pane.

If you intend to run TKGI on GCP, skip this pane when configuring the Tanzu Kubernetes Grid Integrated Edition tile.

TMC Data Protection Feature Requires Privileged TKGI Containers

TMC Data Protection feature supports privileged TKGI containers only. For more information, see Plans in the Installing TKGI topic for your IaaS.

Windows Worker Kubernetes Clusters with Group Managed Service Account Do Not Support Compute Profiles

Windows worker-based Kubernetes clusters integrated with group Managed Service Account (gMSA) cannot be managed using compute profiles.

Windows Worker Kubernetes Clusters on Flannel Do Not Support Compute Profiles

On vSphere with NSX-T networking you can use compute profiles with both Linux and Windows worker‑based Kubernetes clusters. On vSphere with Flannel networking, you can apply compute profiles only to Linux clusters.

TKGI CLI Does Not Prevent Reducing the Control Plane Node Count

TKGI CLI does not prevent accidentally reducing a cluster’s control plane node count using a compute profile.

Warning: Reducing a cluster’s control plane node count can destroy the cluster. Do not scale out or scale in existing master nodes by reconfiguring the TKGI tile or by using a compute profile. Reducing a cluster’s number of control plane nodes may remove a master node and cause the cluster to become inactive.

Windows Cluster Nodes Not Deleted After VM Deleted

Symptom

After you delete a VM using the management console of your infrastructure provider, you notice a Windows worker node that had been on that VM is now in a notReady state.

Solution

1. To identify the leftover node:

   kubectl get no -o wide
   

2. Locate nodes on the returned list that are in a notReady state and have the same IP address as another node in the list.

3. To manually delete a notReady node:

   kubectl delete node NODE-NAME
   

   Where NODE-NAME is the name of the node in the notReady state.

502 Bad Gateway After OIDC Login

Symptom

You experience a “502 Bad Gateway” error from the NSX load balancer after you log in to OIDC.

Explanation

A large response header has exceeded your NSX-T load balancer maximum response header size. The default maximum response header size is 10,240 characters and should be resized to 50,000.

Workaround

If you experience this issue, manually reconfigure your NSX-T request_header_size and response_header_size to 50,000 characters. For information about configuring NSX-T default header sizes, see OIDC Response Header Overflow in the Knowledge Base.

Difficulty Changing Proxy for Windows Workers

You must configure a global proxy in the Tanzu Kubernetes Grid Integrated Edition tile > Networking pane before you create any Windows workers that use the proxy.

You cannot change the proxy configuration for Windows workers in an existing cluster.

Character Limitations in HTTP Proxy Password

For vSphere with NSX-T, the HTTP Proxy password field does not support the following special characters: & or ;.

Error After Modifying Your Harbor Storage Configuration

Symptom

You receive the following error after modifying your existing Harbor installation’s storage configuration:

Error response from daemon: manifest for ... not found: manifest unknown: manifest unknown

Explanation

Harbor does not support modifying an existing Harbor installation’s storage configuration.

Workaround

To modify your Harbor storage configuration, re-install Harbor. Before starting Harbor, configure the new Harbor installation with the desired configuration.

Ingress Controller Statefulset Fails to Start After Resizing Worker Nodes

Symptom

Permissions are removed from your cluster’s files and processes after resizing the persistent disk during a cluster upgrade. The ingress controller statefulset fails to start.

Explanation

When resizing a persistent disk, Bosh migrates the data from the old disk to the new disk but does not copy the files’ extended attributes.

Workaround

To resolve the problem, complete the steps in Ingress controller statefulset fails to start after resize of worker nodes with permission denied in the VMware Tanzu Knowledge Base.

Azure Default Security Group Is Not Automatically Assigned to Cluster VMs

Symptom

You experience issues when configuring a load balancer for a multi-master Kubernetes cluster or creating a service of type LoadBalancer. Additionally, in the Azure portal, the VM > Networking page does not display any inbound and outbound traffic rules for your cluster VMs.

Explanation

As part of configuring the Tanzu Kubernetes Grid Integrated Edition tile for Azure, you enter Default Security Group in the Kubernetes Cloud Provider pane. When you create a Kubernetes cluster, Tanzu Kubernetes Grid Integrated Edition automatically assigns this security group to each VM in the cluster. However, on Azure the automatic assignment may not occur.

As a result, your inbound and outbound traffic rules defined in the security group are not applied to the cluster VMs.

Workaround

If you experience this issue, manually assign the default security group to each VM NIC in your cluster.

One Plan ID Longer than Other Plan IDs

Symptom

One of your plan IDs is one character longer than your other plan IDs.

Explanation

In TKGI, each plan has a unique plan ID. A plan ID is normally a UUID consisting of 32 alphanumeric characters and 4 hyphens. However, the Plan 4 ID consists of 33 alphanumeric characters and 4 hyphens.

Solution

You can safely configure and use Plan 4. The length of the Plan 4 ID does not affect the functionality of Plan 4 clusters.

If you require all plan IDs to have identical length, do not activate or use Plan 4.

Database Cluster Stops After a Database Instance is Stopped

Symptom

After you stop one instance in a multiple-instance database cluster, the cluster stops, or communication between the remaining databases times out, and the entire cluster becomes unreachable.

The following might be in your UAA log:

WSREP has not yet prepared node for application use

Explanation

The database cluster is unable to recover automatically because a member is no longer available to reconcile quorum.

Velero Back Up Fails for vSphere PVs Attached to Clusters on Kubernetes v1.20 and Later

Symptom

Backing up vSphere persistent volumes using Velero fails and your Velero backup log includes the following error:

rpc error: code = Unknown desc = Failed during IsObjectBlocked check: Could not translate selfLink to CRD name

Explanation

This is a known issue when backing up clusters on Kubernetes v1.20 and later using the Velero Plugin for vSphere v1.1.0 or earlier.

Workaround

To resolve the problem, complete the steps in Velero backups of vSphere persistent volumes fail on Kubernetes clusters version 1.20 or higher (83314) in the VMware Tanzu Knowledge Base.

Creating Two Windows Clusters at the Same Time Fails

Symptom

The first time that you try to create two Windows clusters at the same time, the creation of one of the clusters fails. If you run pks cluster CLUSTER-NAME to examine the last action taken on the cluster, you see the following:

Last Action: Create
Last Action State: failed
Last Action Description: Instance provisioning failed: There was a problem completing your request.
. . .
operation: create, error-message: Failed to acquire lock
. . .
locking task id is 111, description: 'create deployment'

Explanation

This is a known issue that occurs the first time that you create two Windows clusters concurrently.

Workaround

Recreate the failed cluster. This issue only occurs the first time that you create two Windows clusters concurrently.

Deleted Clusters are Listed in Cluster Lists

Symptom

After running tkgi delete-cluster and cluster deletion has completed, the deleted cluster continues to be listed when running tkgi clusters.

Workaround

You must manually remove the deleted cluster using a customized version of the ncp_cleanup script. For more information, see Deleting a Tanzu Kubernetes Grid Integrated Edition cluster with “tkgi delete-cluster” stuck “in progress” status in the VMware Tanzu Knowledge Base.

Creating a New Cluster Fails With the Error 'IP Is Already Allocated’

Symptom

Creating a new cluster fails while using the Antrea CNI. The coreDNS add-on errand logs an error similar to the following:

The Service \"kube-dns\" is invalid: spec.clusterIPs: Invalid value: []string{\"10.100.200.2\"}: failed to allocated ip:10.100.200.2 with error:provided IP is already allocated\n"

Workaround

Delete the failed cluster and run tkgi create-cluster again.

BOSH Director Logs the Error 'Duplicate vm extension name’

Symptom

After you uninstall TKGI, then reinstall TKGI in the same environment, BOSH Director logs errors similar to the following:

.../gems/bosh-director-0.0.0/lib/bosh/director/deployment_plan/cloud_manifest_parser.rb:120:in `parse_vm_extensions': Duplicate vm extension name 'disk_enable_uuid' (Bosh::Director::DeploymentDuplicateVmExtensionName)

Explanation

The pivotal-container-service cloud-config was not removed when you uninstalled the TKGI tile, and it remained active. When you reinstalled the TKGI tile, an additional pivotal-container-service cloud-config was created, causing the metrics_server to fall into a crash-loop state.

Workaround

You must manually remove the pivotal-container-service cloud-config after removing your TKGI deployment, including after removing the TKGI tile from Ops Manager.

For more information, see “Duplicate vm extension name” error when metrics_server runs on Director VM in Tanzu Kubernetes Grid Integrated Edition in the VMware Tanzu Community Knowledge Base.

The TKGI API FQDN Must Not Include Trailing Whitespace

Symptom

Your TKGI logs include the following error:

'uaa'. Errors are:- Error filling in template 'uaa.yml.erb' (line 59: Client redirect-uri is invalid: uaa.clients.pks_cli.redirect-uri Client redirect-uri is invalid: uaa.clients.pks_cluster_client.redirect-uri)

Explanation

The TKGI API fully-qualified domain name (FQDN) for your cluster contains leading or trailing whitespace.

Workaround

Do not include whitespace in the TKGI tile API Hostname (FQDN) field.

SAML Authentication Requests Are Always Signed

Symptom

After you disable the SAML Identity Provider Sign Authentication Requests setting on the Tanzu Kubernetes Grid Integrated Edition tile, SAML IdP authentication requests continue to be signed.

TKGI Management Console v1.12.0

Release Date: September 9, 2021

Note: Tanzu Kubernetes Grid Integrated Edition Management Console provides an opinionated installation of TKGI. The supported versions may differ from or be more limited than what is generally supported by TKGI.

Product Snapshot

* Components marked with an asterisk have been updated.

Upgrade Path

The supported upgrade path to Tanzu Kubernetes Grid Integrated Edition Management Console v1.12.0 is from Tanzu Kubernetes Grid Integrated Edition v1.11.0 and later.

Features and Resolved Issues

TKGI Management Console v1.12.0 has the following features and enhancements:

TKGI Management Console v1.12.0 has the following resolved issues:

Deprecations

The following TKGI features have been deprecated or removed from TKGI Management Console v1.12:

• Support for DenyEscalatingExec has been removed from Kubernetes v1.21 and can no longer be configured in the TKGI Management Console. For more information, see DenyEscalatingExec in the Kubernetes documentation.
  

Known Issues

The Tanzu Kubernetes Grid Integrated Edition Management Console v1.12.0 has the following known issues:

vRealize Log Insight Integration Does Not Support HTTPS Connections

Symptom

The Tanzu Kubernetes Grid Integrated Edition Management Console integration to vRealize Log Insight does not support connections to the HTTPS port on the vRealize Log Insight server.

Workaround

1. Use SSH to log in to the Tanzu Kubernetes Grid Integrated Edition Management Console appliance VM.
2. Open the file /lib/systemd/system/pks-loginsight.service in a text editor.
3. Add -e LOG_SERVER_ENABLE_SSL_VERIFY=false.

4. Set -e LOG_SERVER_USE_SSL=true.

   The resulting file should look like the following example:

   ExecStart=/bin/docker run --privileged --restart=always --network=pks
   -v /var/log/journal:/var/log/journal
   --name=pks-loginsight
   -e TYPE=gear2-vm
   -e LOG_SERVER_HOST=${LOGINSIGHT_HOST}
   -e LOG_SERVER_PORT=${LOGINSIGHT_PORT}
   -e LOG_SERVER_ENABLE_SSL_VERIFY=false
   -e LOG_SERVER_USE_SSL=true
   -e LOG_SERVER_AGENT_ID=${LOGINSIGHT_ID}
   pksoctopus/vrli-journald:v07092019
   

5. Save the file and run systemctl daemon-reload.

6. To restart the vRealize Log Insight service, run systemctl restart pks-loginsight.service.

Tanzu Kubernetes Grid Integrated Edition Management Console can now send logs to the HTTPS port on the vRealize Log Insight server.

vSphere HA causes Management Console ovfenv Data Corruption

Symptom

If you enable vSphere HA on a cluster, if the TKGI Management Console appliance VM is running on a host in that cluster, and if the host reboots, vSphere HA recreates a new TKGI Management Console appliance VM on another host in the cluster. Due to an issue with vSphere HA, the ovfenv data for the newly created appliance VM is corrupted and the new appliance VM does not boot up with the correct network configuration.

Workaround

• In the vSphere Client, right-click the appliance VM and select Power > Shut Down Guest OS.
• Right-click the appliance again and select Edit Settings.
• Select VM Options and click OK.
• Verify under Recent Tasks that a Reconfigure virtual machine task has run on the appliance VM.
• Power on the appliance VM.

Base64 encoded file arguments are not decoded in Kubernetes profiles

Symptom

Some file arguments in Kubernetes profiles are base64 encoded. When the management console displays the Kubernetes profile, some file arguments are not decoded.

Workaround

Run echo "$content" | base64 --decode

Network profiles not immediately selectable

Symptom

If you create network profiles and then try to apply them in the Create Cluster page, the new profiles are not available for selection.

Workaround

Log out of the management console and log back in again.

Real-Time IP information not displayed for network profiles

Symptom

In the cluster summary page, only default IP pool, pod IP block, node IP block values are displayed, rather than the real-time values from the associated network profile.

Workaround

None

Error After Modifying Your Harbor Storage Configuration

Symptom

You receive the following error after modifying your existing Harbor installation’s storage configuration:

Error response from daemon: manifest for ... not found: manifest unknown: manifest unknown

Explanation

Harbor does not support modifying an existing Harbor installation’s storage configuration.

Workaround

To modify your Harbor storage configuration, re-install Harbor. Before starting Harbor, configure the new Harbor installation with the desired configuration.

Windows Stemcells Must be Re-Imported After Upgrading Ops Manager

Symptom

After upgrading Ops Manager, your Management Console does not recognize a Windows stemcell imported when using the prior version of Ops Manager.

Workaround

If your Management Console does not recognize a Windows stemcell after upgrading Ops Manager:

1. Re-import your previously imported Windows stemcell.
   
2. Apply Changes to TKGI MC.
   

Your New Clusters Are Not Shown In Tanzu Mission Control

Symptom

After you create a cluster, Tanzu Mission Control does not include the cluster in cluster lists. You have a “Resource not found” error similar to the following in your BOSH logs:

Cluster Name in TMC: cluster-1
Cluster Name Prefix: tkgi-my-prefix-
Group Name in TMC: my-prefix-clusters
Cluster Description in TMC: VMware Enterprise PKS Attaching cluster ''tkgi-my-prefix-cluster-1'' to TMC 
Fetching token successful 
request POST:/v1alpha1/clusters, 
response 404 Not Found:{"error":"Resource not found - clustergroup(my-prefix-clusters) 
org id(d859dc9f-g622-426d-8c91-939a9f13dea9)",
"code":5,"message":"Resource not found - clustergroup(my-prefix-clusters)

Explanation

The cluster group you assign a cluster to must be defined in Tanzu Mission Control before you assign your cluster to the cluster group in the TKGI Management Console.

Workaround

To resolve the problem, complete the steps in Attaching a Tanzu Kubernetes Grid Integrated (TKGI) cluster to Tanzu Mission Control (TMC) fails with “Resource not found - clustergroup(cluster-group-name)” in the VMware Tanzu Knowledge Base.