TMC Self-Managed 1.2 Release Notes

VMware Tanzu Mission Control 1.2 \| 29 MAR 2024 Check for additions and updates to these release notes.

VMware Tanzu Mission Control 1.2 | 29 MAR 2024

Check for additions and updates to these release notes.

Welcome to the Release Notes for VMware Tanzu Mission Control Self-Managed. Here you find posts about new features, patches, and bug fixes for the platform.

Tanzu Mission Control Self-Managed is a comprehensive API-driven cluster management platform, provided through a packaged deployment model, that allows you to monitor and manage your fleet of Kubernetes clusters from a single point of control. Tanzu Mission Control Self-Managed builds on the success of the SaaS deployment model for Tanzu Mission Control by enabling you to deploy the cluster management stack atop your own infrastructure.

What's New in version 1.2

Tanzu Mission Control Self-Managed 1.2 supports deployment to and lifecycle management of the following Tanzu Kubernetes Grid clusters:

Cluster type	Environment
Tanzu Kubernetes Grid Service clusters running in vSphere with Tanzu	vSphere 8.0 (Kubernetes 1.26.x and 1.25.x) vSphere 7.0 (Kubernetes 1.26.x, 1.25.x, and 1.24.x)
TKG 2.5.0 (Kubernetes 1.28.4, 1.27.8, and 1.26.11)	vSphere 8.0 and vSphere 7.0 Note: If you are using TKG version 2.3 or later in an air-gapped environment, make sure you review the TKG setup documentation for an internet-restricted environment: https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/2.5/tkg-deploy-mc/mgmt-reqs-prep-offline.html
TKG 2.4.x (Kubernetes 1.27.5, 1.26.8, and 1.25.13)
TKG 2.3.x (Kubernetes 1.26.8, 1.25.13, and 1.24.17)

New Features and Improvements

TMC Self-Managed 1.2 service updates
New features and enhancements for 1.2
Known Issues in 1.2

TMC Self-Managed 1.2 service updates

Added support for sAMAccountName for Active Directory user accounts

TMC Self-Managed now accepts sAMAccountName as a valid configuration value for connecting Active Directory users to TMC Self-Managed deployments. This capability allows you to authenticate users that use "power user" accounts, without the email address attribute set, to incorporate those accounts with a TMC deployment.
Added support for dynamic configuration changes

You can now update configuration values for your TMC Self-Managed deployment without doing a complete reinstall. You can modify your values.yaml file with updated configuration and then an update command to apply your changes. This capability enables you, for example, to update the TMC Self-Managed stack size from small to medium to increase management scale capabilities without a complete reinstall. For more information, see Dynamically update the stack size of your TMC Self-Managed deployment in Installing and Running VMware TMC Self-Managed.
Updated FluxCD version for continuous delivery and Helm capabilities

The version of FluxCD used by the continuous delivery (CD) and Helm package management features of Tanzu Mission Control (TMC) is updated to 2.1.x. When you enable CD or Helm on clusters managed through TMC Self-Managed, it installs FluxCD v2.1.x.

This update applies to individual clusters on which you enable CD or Helm, as well as clusters that are part of a cluster group on which you enable CD or Helm.

New features and enhancements for 1.2

Added support for CSI volume snapshots

In addition to File System Backup (FSB), you can now use Container Storage Interface (CSI) snapshot support for backing up and restoring Kubernetes volumes in TMC Self-Managed. You can choose FSB as well as CSI snapshot method during backup and restore operations. For more details on FSB and CSI snapshot usage, see Data Protection in VMware Tanzu Mission Control Concepts.

For information about using the FSB and CSI during backup operation in Tanzu Mission Control Self-Managed, see in Back Up the Data Resources in Your Cluster in Using VMware Tanzu Mission Control.
Added support for data protection for cluster groups

TMC Self-Managed now allows you to enable data protection for a cluster group. This capability allows you to configure recurring backups for all the clusters in a group, or clusters based on names, or clusters based on Tanzu Mission Control labels. New clusters added to the cluster group inherit the configured schedule for the group. Restore operations are supported only at the individual cluster level; restore operations are not available at the cluster group level.

For more information, see Enable Data Protection on a Cluster Group in Using VMware Tanzu Mission Control.
Updated Velero to version 1.12.3

The version of Velero used by the data protection features of Tanzu Mission Control is updated to 1.12.3. This Velero update includes bug fixes in CSI snapshot, data mover, and volume restore. Refer to the changelog for details.
Added support for ability to edit a recurring backup schedule

TMC Self-Managed now allows you to edit a schedule of recurring backups for your clusters, created at the cluster level and cluster group level. While editing backup schedule, you can change the advanced options for Kubernetes resources, volume backup options, target location, backup recurrence, and retention period. However, you cannot change the scope of the backup of Kubernetes resources between full cluster, selected namespace, and label selector.
Added option to force the deletion of a backup

TMC Self-Managed now allows you force the deletion of the backup of a cluster. When the configured target location is no longer accessible from the cluster, the backup delete operation cannot complete and keeps running. You now have the option to "force delete" the backup, which removes the backup entry from TMC, and allows you to delete the backup from the target location manually.

Known Issues in 1.2

Inspections fail on TKG Service workload clusters with Kubernetes version 1.26 and later

For TKG Service workload clusters with Kubernetes version 1.26 or later, running in vSphere with Tanzu, the Pod Security Admission is set to "enforce" by default. As a result, inspections are unable to run until you add the required label (pod-security.kubernetes.io/enforce: privileged) to the namespace (image-pull-xxxx) created during the inspection run.

Workaround: To allow the inspection to run, you need to start the inspection and then add the label to the namespace created by the inspection, as described in Start a Cluster Inspection inUsing VMware Tanzu Mission Control.
Users unable to access TMC console after successful install

After a successful installation of TMC Self-Managed, users are unable to login/access the TMC user interface. This is often a result of previous failed installs leaving behind stale secrets.

Workaround: To enable access to TMC Self-Managed in this situation, follow the process documented in Unable to log in to the TMC console after installation in the troubleshooting section of Installing and Running Tanzu Mission Control Self-Managed to delete stale components, such as secrets and dynamic OIDC client.