Service Installer for VMware Tanzu 2.2.0.x Release Notes

Except where noted, these release notes apply to all v2.2.x patch versions of Service Installer for VMware Tanzu (SIVT).

What’s New in 2.2.0.1

The following new features and support are added in 2.2.0.1:

Support for v1alpha3 APIs on vSphere 8.0 for TKG service deployments.

This release resolves the following issues:

Deployments of TKG Service using Tanzu Standard License with 60 days Evaluation mode are allowed.
UI: Fixes on Configure and Upload flows for VMC.

What’s New in 2.2.0

The following new features and support are added in 2.2.0.

Service Installer for VMware Tanzu (SIVT) adds support for the following:
- Tanzu Kubernetes Grid (TKG) 2.2.0.
- NSX ALB Essentials license in addition to the existing support for the Enterprise license for Tanzu Kubernetes Grid (TKG) standalone management and Supervisor on VDS platforms.
- Version control for the deployment JSON file generated from the SIVT user interface.
- TKG 2.1.1 for non-compliant deployment on AWS and TKG 1.6.1 (FIPS) for compliant deployment.
Use of TMC APIs for TMC related operations. This release does not use TMC CLI.
- TMC API code changes are ported to VMC along with other code enhancements.
- TMC API: Worker node count passed as control plane node count to API payload for shared and workload cluster.

Note
For deployments on Azure, SIVT supports older versions of Tanzu Kubernetes Grid. For supported TKG versions, see Service Installer for VMware Tanzu Support Matrix.

Resolved Issues

Backend Check for Kubernetes OVA version of Shared and Workload clusters in JSON files is missing.
Fluent-bit extension failing for TKGs proxy.
UI: VDS Configure options has a bug on Custom repo page leading to AVI not getting loaded.
Inconsistent naming of networks / port groups in docs.
Activating AVI L7 on vSphere with NSXT environments over NodePortLocal mode fails to bring-up AKO pods.
Implement pre-check to handle ‘AKO POD deployment failure if cluster name has more than 25 characters.’

Known Issues

Integration of TMC with vSphere 8.0 is not supported with SIVT due to limited support for cluster classes.
TO and TSM integration fails with the latest version of kubernetes 1.25.x for TKGm 2.2.0 deployment
There is a known product issue with Harbor(2.6.x) when deployed on a Workload cluster for vSphere with Tanzu deployments.
There is a known issue for fluent-bit extensions deployment when grafana and prometheus is not selected alongside fluent-bit for vsphere TKG multi cloud.
There is a known TMC issue for TKGs extension deployment, Kapp running on the cluster doesn’t support Tanzu packaging.
FIPS/STIG compliant deployment for Tanzu Kubernetes Grid 2.1.1 onwards is not supported in SIVT.
The size of SIVT OVA with Harbor and Tanzu Kubernetes Grid dependency is increased to 25 GB as downloading the Kube version specific Tanzu Kubernetes Grid binary download is not supported in ‘tanzu isolated-cluster plugin’.
Service Installer for VMware Tanzu is unable to fetch cluster images from the content library. This happens due to a known issue with Tanzu on vSphere. The subscribed content library needs to be synced manually sometimes to update with the images.
VCD API call takes time depending on environment configuration , re-trigger the SIVT command after 1 min delay
Creating ALB Service Engine Group assignment to Edge Gateway fails intermittently. Terraform provider issue
SIVT supposed to download Ubuntu-2004-kube-v1.22.9.ova version, right now it is downloading Ubuntu-2004-kube-v1.23.8.ova version. Note: If user need specific version of Ubuntu + K8S ova version, download the same from marketplace and upload it to the K8S catalog.
There is a known issue with Harbor(2.6.1) extensions deployment on Tanzu Kubernetes Grid AWS compliant deployment.
In case you are using proxy with self-signed or custom CA certificate, SIVT fails to pull the kind image while deploying Tanzu Kubernetes Grid management cluster in a vSphere VDS environment.
Resolution: Before initiating the deployment with SIVT, perform the following steps:
1. Import the proxy certificate into the SIVT VM.
2. Run the following commands:
```
cat proxy-cert.pem >> /etc/pki/tls/certs/ca-bundle.crt
systemctl restart docker
```
In case you are using SIVT OVA with embedded Harbor, if Docker restarts or SIVT VM reboots, it may result in embedded Harbor failure.

Resolution: Perform the following steps:
1. SSH to the SIVT VM.
2. Go to /opt/vmware/arcas/tools/harbor
3. Run the following commands:
```
docker-compose stop
find common/ -type f -exec chmod 0755 \{\} \;
docker-compose up -d
```

Download

Download the Service Installer OVA and AWS solutions from VMware Marketplace: Service Installer for VMware Tanzu.