VMware Tanzu Application Service for VMs v2.11 Release Notes
Page last updated:
This topic contains release notes for VMware Tanzu Application Service for VMs (TAS for VMs) v2.11.
Ops Manager is certified by the Cloud Foundry Foundation for 2021.
For more information about the Cloud Foundry Certified Provider Program, see How Do I Become a Certified Provider? on the Cloud Foundry website.
Release Date: March 30, 2021
To upgrade to TAS for VMs v2.11, see Configuring TAS for VMs for Upgrades.
When upgrading to TAS for VMs v2.11, be aware of the following upgrade considerations:
TAS for VMs v2.11 is compatible with Ops Manager v2.10. If you are using a previous version of Ops Manager, you must upgrade to Ops Manager v2.10 before you upgrade to TAS for VMs v2.11.
If you are upgrading from Pivotal Application Service (PAS) v2.7 or TAS for VMs v2.8 and later, you can upgrade directly to TAS for VMs v2.11. TAS for VMs v2.11 is an LTS version of TAS for VMs. See Long-Term Support for TAS for VMs v2.11 below for more information.
If you are upgrading from PAS v2.6 or earlier, you must upgrade to PAS v2.7 before you upgrade to TAS for VMs v2.11.
Some partner service tiles may be incompatible with TAS for VMs v2.11. VMware is working with partners to ensure their tiles are updated to work with the latest versions of TAS for VMs.
For information about which partner service releases are currently compatible with TAS for VMs v2.11, review the appropriate partners services release documentation at https://docs.pivotal.io or contact the partner organization that produces the tile.
TAS for VMs v2.11 includes the following major features:
TAS for VMs v2.11 is a long-term supported (LTS) version of TAS for VMs. TAS for VMs v2.11 will be supported through April 2024.
Over the lifecycle of TAS for VMs v2.11, VMware will release security patches that occasionally include feature enhancements and maintenance updates. VMware will also continue to release new versions of TAS for VMs.
You can jump upgrade directly from previous versions of TAS for VMs to the LTS version of TAS for VMs. For more information, see Jump Upgrading to TAS for VMs v2.11.
TAS for VMs v2.11 can be deployed on VMware Cloud Foundation (VCF) v4.1. For instructions and more information, see Deploying TAS for VMs to VCF.
TAS for VMs v2.11 can be deployed to VMware Cloud (VMC) on Amazon Web Services (AWS). For instructions and more information, see Deploying TAS for VMs to VMC.
TAS for VMs v2.11 introduces RFC3339 log format support for several TAS for VMs components. You can configure these components to produce logs with human-readable RFC3339 timestamps with the Timestamp format for component logs configuration option in the TAS for VMs tile. Logs that use human-readable timestamps are often easier to debug.
RFC3339-formatted timestamps follow the RFC3339 spec, include nine points of precision where possible, and are in UTC. For example:
For more information about configuring the Timestamp format for component logs field, see System Logging in Configuring TAS for VMs.
In TAS for VMs v2.11.0, if you select the Converge to human-readable RFC3339 format option under Timestamp format for component logs, then the following components and related jobs use RFC3339 timestamps:
This new feature is related to a breaking change. For more information, see Timestamps for Component Logs in Diego Logs when Upgrading below.
TAS for VMs v2.11 supports Cloud Foundry V3 APIs. This feature improves response time when working with services. Use the Cloud Foundry V3 API endpoints when listing, creating, or modifying any service that works with TAS for VMs v2.11 and later.
TAS for VMs v2.11 includes the following resolved issues:
When you configure the CredHub server for TAS for VMs, you must select a primary encryption key. In TAS for VMs v2.11, if you do not select a primary encryption key, or if you mark more than one key as the primary encryption key, deployment fails more quickly than in previous releases of TAS for VMs.
For more information, see Configure CredHub in Configuring TAS for VMs.
For greater stability, Apps Manager uses the Cloud Controller API (CAPI) V2 endpoint instead of the experimental V3 endpoint.
In TAS for VMs, disabled service plans are handled gracefully in the Apps Manager UI.
TAS for VMs v2.11 includes the following breaking changes:
In TAS for VMs v2.11.0 and later, the option to disable SSL certificate verification for an environment is removed.
Before you upgrade to TAS for VMs v2.11, you must deselect the option to disable SSL certificate verification in the Networking pane of the TAS for VMs tile. For more information, see Configure Networking in Configuring TAS for VMs.
If the Disable SSL certificate verification for this environment option is enabled when you try to upgrade to TAS for VMs, the upgrade fails with the following error:
attempt to upgrade to PAS 2.11+ with Skip SSL Verification enabled, please disable Skip SSL Verification prior to upgrade by un-checking "Disable SSL certificate verification for this environment" under "Networking"
If you plan to automate the installation of TAS for VMs v2.11, you must remove references to the corresponding property
Gorouter Update to Golang v1.15 Introduces Stricter Transfer-Encoding Header Standards in TAS for VMs v2.11.0 and Later
In TAS for VMs v2.11.0 and later, stricter header standards break Spring apps that incorrectly set the header.
For information about how to avoid this breaking change, see Applications on TAS for VMs get 502 chunked response error in the Knowledge Base. You must complete the resolution steps described in this Knowledge Base article before you upgrade to TAS for VMs v2.11.0 or later.
Note: This breaking change was also present in Pivotal Application Service (PAS) v2.7.30, PAS v2.8.24, TAS for VMs v2.9.18, and TAS for VMs v2.10.10. If you are on any of these versions or earlier, you must upgrade to v2.7.31, v2.8.25, v2.9.21, or v2.10.11 before upgrading or jump upgrading to 2.11.0 or later. For more information, see Applications on TAS for VMs get 502 chunked response error.
The Timestamp format for component logs feature replaces the Format of timestamps in Diego logs feature in the App Containers pane of the TAS for VMs tile. However, when you upgrade to TAS for VMs v2.11, the option that was selected under Format of timestamps in Diego logs in your previous deployment is applied to Timestamp format for component logs. For more information, see Timestamp Format for Component Logs Replaces Timestamp Format for Diego Logs.
You cannot upgrade to TAS for VMs v2.11 if you are using Dynamic Egress policies.
To see if you have Dynamic Egress policies, see List Egress Policies in the TAS for VMs v2.10 documentation.
To delete each of your policies, see Delete an Egress Policy in the TAS for VMs v2.10 documentation.
There are no known issues in this release of TAS for VMs.