Tanzu Operations Manager v3.0 partners release notes

You can learn about the changes in VMware Tanzu Operations Manager v3.0 that might be relevant to partner service tiles.

For information about changes introduced in Tanzu Operations Manager v3.0, and any breaking changes, see Tanzu Operations Manager v3.0 Release Notes.

Releases

Metadata version 3.0.4

Shipped in Tanzu Operations Manager v3.0.29

• [Feature] Tiles can opt-in to read-only credentials to communicate with the BOSH Director using the bosh_read_creds property. For more information, see bosh_read_creds on the Property and template references page.

Metadata version 3.0.3

Shipped in Tanzu Operations Manager v3.0.24

• [Feature] Tiles can use the migrated_from property to rename a job. For more information, see Update deployed job names using the migrated_from job property.

Metadata version 3.0.2

November 13, 2023

Shipped in Tanzu Operations Manager v3.0.19

• [Feature] vcenter_ca_certificate added to VsphereConfigurationVerifier. When vcenter_ca_certificate is provided, the vCenter server certificates are validated against the provided CA or certificate chain. If it’s not provided or a blank value is configured, TLS connections are established but the certificate for the vCenter server is not validated.

Metadata version 3.0.1

Shipped in Tanzu Operations Manager v3.0.16

• [Bug Fix] Using the $director dollar context within manifest snippets for collections and selectors no longer causes Tanzu Operations Manager to crash.

Metadata version 3.0.0

Shipped in Tanzu Operations Manager v3.0.0

No new features since Tanzu Operations Manager v2.10.

Known issues and breaking changes

This section contains known issues and breaking changes that can affect tile development by partners. Not all of the items below will apply to all tiles.

Partners who have a pre-release binary agreement on file can test their offerings’ compatibility by claiming a TPCF 10.0 environment. VMware recommends that ecosystem and partner teams test and declare their tiles’ compatibility with TAS 10.0 promptly, to ensure a smooth upgrade for customers.

Removed accessors

The metrics_server_enabled accessor has been deprecated due to the removal of the BOSH System Metrics Server release in Tanzu Operations Manager 3.0. The accessor now always returns false.

The following accessors have been removed. If you reference them, invalid data is returned, but it does not cause an error:

• bosh_metrics_forwarder_client_name
• bosh_metrics_forwarder_client_secret

Gorouter uses port 7070 by default for internal route services instead of a random available port

Why Should I Be Concerned About This Change?

This change is relevant to tiles that depend on a known port for the Gorouter.

How Can I Tell If I’m Impacted?

SSH into a router VM and use lsof -Pi to determine if port 7070 is being used. Be sure to check any routers deployed by IST as well.

What Should I Do About It?

If your foundation is impacted, use Tanzu Operations Manager to configure use of a different port.

For TAS, go to the Networking tab and scroll down to the Route Services section. If route services are enabled, you will see a text box labeled “The port used for internal route services requests.” Set the value to a known available port, or set the value to 0 to allow the operating system to choose an available port at deploy time.

For IST, go to the Networking tab and scroll down to the text box labeled “The port used for internal route services requests.” Follow the same instructions as you did for TAS.

CLI v7 deprecation after TAS for VMs 10.0

Why Should I Be Concerned About This Change?

Starting with the next major TAS for VMs release after v10.0, cf CLI v7 will not be supported. Only CLI v8 will get security updates and feature upgrades.

How Can I Tell If I’m Impacted?

Check the existing CLI version by running cf version command in a terminal. If it displays cf version 7.x.x, CLI v7 is being used.

What Should I Do About It?

Upgrade to CLI v8.