Ops Manager v2.10 and Runtime Breaking Changes

This topic describes the breaking changes you need to be aware of when upgrading to v2.10. For more information about important preparation steps you must follow before beginning an upgrade, see Upgrading Ops Manager.

Ops Manager

See the following Ops Manager breaking change:

CredHub Maestro Removes the “update-transitional latest” Command

Ops Manager v2.10 includes CredHub Maestro v8.0. In this version of CredHub Maestro, the maestro update-transitional latest command is removed.

If you have scripts that rely on the maestro update-transitional latest command, remove references to the command before you upgrade to Ops Manager v2.10.

In CredHub Maestro v8.0, you run maestro regenerate ca to regenerate a certificate authority (CA) and mark the latest version of the CA as transitional. This command performs both actions, while previous versions of CredHub Maestro use a separate command for each task.

For information about rotating CAs and certificates using CredHub Maestro, see Advanced Certificate Rotation with CredHub Maestro.

VMware Tanzu Application Service for VMs (TAS for VMs)

See the following TAS for VMs breaking changes:

Timestamp Format for Component Logs Replaces Timestamp Format for Diego Logs

The Format of timestamps in Diego logs feature is removed from the App Containers pane of the TAS for VMs tile. It is replaced by Timestamp format for component logs in the System Logging pane of the TAS for VMs tile.

TAS for VMs v2.10 automatically configures Timestamp format for component logs based on how you configured Format of timestamps in Diego logs in TAS for VMs v2.9:

  • If the RFC3339 timestamps option for Format of timestamps in Diego logs is selected before you upgrade to TAS for VMs v2.10, then the Converge to human-readable RFC3339 format option for Timestamp format for component logs is selected in TAS for VMs v2.10 by default. Converge to human-readable RFC3339 format configures TAS for VMs to use RFC3339 timestamps in the logs of several TAS for VMs components.

  • If the Seconds since the Unix epoch option for Format of timestamps in Diego logs is selected before you upgrade to TAS for VMs v2.10, then the Maintain previous format option for Timestamp format for component logs is selected in TAS for VMs v2.10 by default.

To avoid breaking changes associated with this update, you must:

  • Update any automation scripts that reference the removed Format of timestamps in Diego logs feature.

  • If RFC3339 timestamps is selected for Format of timestamps in Diego logs before you upgrade to TAS for VMs v2.10, update any external monitoring configuration to account for RFC3339 timestamps in the logs for several TAS for VMs components. For a list of TAS for VMs components that support RFC3339 timestamps in TAS for VMs v2.10, see Optionally Use Human-Readable Timestamps for Component Logs in VMware Tanzu Application Service for VMs v2.10 Release Notes.

For more information about configuring RFC3339 timestamps for component logs, see System Logging in Configuring TAS for VMs.

Aggregate Syslog Drains Contain Logs Only

In TAS for VMs v2.10, aggregate syslog drains contain only logs by default, and do not contain metrics. If you rely on metrics sent through aggregate syslog drains, you must add ?include-metrics-deprecated=true to your aggregate drain URLs to continue to receive metrics in the drains.

For more information, see Aggregate Syslog Drains Contain Logs Only in the TAS for VMs v2.10 Release Notes.

VMware Tanzu Application Service for VMs [Windows] (TAS for VMs [Windows])

See the following TAS for VMs [Windows] breaking changes:

Isolation Segment

There are no breaking changes in this release of Isolation Segment.

End-of-Life Components

This section lists of components that are either at their end-of-life (EOL) or nearing EOL.

Buildpack Support Changes

This section lists support changes to buildpacks associated with this release:

  • NGINX Buildpack: NGINX v1.16.x and v1.17.x are removed from the NGINX buildpack v1.1.12 and later because NGINX v1.16.x and v1.17.x are out of support.

  • Node.js Buildpack: Node.js v13.x is removed from the Node.js buildpack v1.7.22 and later because Node.js v13.x is out of support.

  • PHP Buildpack: NGINX v1.16.x and v1.17.x are removed from the PHP buildpack v4.4.20 and later because NGINX v1.16.x and v1.17.x are out of support.

If your apps depend on any of these language distributions and use the buildpacks that are packaged with TAS for VMs, consider updating the apps and their dependencies before upgrading to TAS for VMs v2.10.

AWS S3 Path-Based Access Model

On September 30, 2020, AWS will no longer support the path-based model for accessing S3 buckets. Support for the path-based model will continue for S3 buckets created on or before September 30, 2020. S3 buckets created after that date must be accessed using the virtual-hosted model.

For more information, see Amazon S3 Path Deprecation Plan – The Rest of the Story on the AWS News Blog.