You can learn about the changes in VMware Tanzu Operations Manager v2.10 that might be relevant to partner service tiles.
For information about changes introduced in Tanzu Operations Manager v2.10, and any breaking changes, see Tanzu Operations Manager v2.10 Release Notes.
Shipped in Tanzu Operations Manager v2.10.62
$director
dollar context within manifest snippets for collections and selectors no longer causes Tanzu Operations Manager to crash.Shipped in Tanzu Operations Manager v2.10.33
ubuntu-jammy
can now be specified as a stemcell OS required by a tile.Shipped in Tanzu Operations Manager v2.10.21
BlobstoreVerifier
now takes an optional ca_cert
property. When specified, the certificate presented by the S3 blobstore endpoint is verified against the provided CA or self-signed certificate.Shipped in Tanzu Operations Manager v2.10.0
In TAS for VMs v2.10, you can modify the timestamp format of TAS for VMs component logs.
TAS for VMs v2.10 removes the diego_log_timestamp_format
tile property and replaces it with the logging_timestamp_format
property, which allows operators to configure human-readable timestamps across TAS for VMs components. Most, but not all, TAS for VMs components can support the RFC3339 timestamp format.
For more information about the RFC3339 timestamp format in TAS for VMs, see VMware Tanzu Application Service Documentation.
This feature might affect any partner tiles that parse or consume TAS for VMs component logs.
For more information, see Timestamp Format for Component Logs Replaces Timestamp Format for Diego Logs.
Tanzu Operations Manager v2.10 runs CredHub Maestro to perform the bulk rotation of various CAs and certificates within a foundation.
To ensure compatibility with Tanzu Operations Manager API certificate rotation and CredHub Maestro, you must use the concatenated LEAF-CERTIFICATE-NAME.ca
format when referencing CAs that sign leaf certificates in your tile’s property configuration. Do not reference the CA directly with the format CA-CERTIFICATE-NAME.certificate
.
The .ca
accessor format returns a concatenated version of the CA, which includes the older and newer CA. The concatenated version ensures that jobs using leaf certificates do not lose trusted state during CA rotation, and results in the lowest amount of downtime for your tile’s services during certificate rotation.
For more information and configuration examples, see Reference Existing CAs and Certificates in CredHub Variables.
Here are the known issues in this release that might affect tile development for partners.
The following accessors have been removed. If you reference them, invalid data is returned, but does not cause an error:
bosh_metrics_forwarder_client_name
bosh_metrics_forwarder_client_secret