VMware Tanzu Application Service for VMs [Windows] v2.10 Release Notes

Page last updated:

This topic contains release notes for VMware Tanzu Application Service for VMs [Windows] v2.10.

For the feature highlights of this release, read the blog post VMware Tanzu Application Service 2.10 Adds New CLI, Eases Upgrades with More Flexible Control Plane or see New Features in TAS for VMs [Windows] v2.10.

Because VMware uses the Percona Distribution for MySQL, expect a time lag between Oracle releasing a MySQL patch and VMware releasing TAS for VMs [Windows] containing that patch.

Warning: Windows stemcells v2019.44 and later include a version of tar that is incompatible with winfs2019-release v2.33.1 and earlier. For more information, see Windows Stemcell v2019.44 is Incompatible with winfs2019-release v2.33.1 and Earlier in Known Issues.

Before you install the tile, refer to the Windows Stemcell Compatibility Matrix.

Releases

2.10.28

Release Date: 08/10/2022

2.10.27

Release Date: 07/18/2022

• Bump diego to version 2.62.0
• Bump garden-runc to version 1.20.8

2.10.26

Release Date: 06/23/2022

Warning: Upcoming reduction in maintenance and security release coverage! In future patches, no sooner than July 1st 2022, some TAS components will become more strict about the protocols used in TLS communications, causing integrations with systems using older, insecure protocols to fail. Specifically, components built using the Go programming language will no longer support TLS 1.0 or 1.1, or certificates using SHA-1. In order to avoid breaking changes in this version line, (which has reached its End of General Support,) these components will no longer be updated with bug and security fixes in any patches that may be released. To continue receiving maintenance and security releases, upgrade to a version of TAS that remains in general support.

• Bump diego to version 2.62.0

2.10.25

Release Date: 06/09/2022

Warning: Breaking change. This version contains Diego 2.64.0, which bumps to Go 1.18. Go 1.18 no longer supports TLS 1.0 and 1.1 connections or certificates with a SHA-1 checksum. This is most likely to affect connections with external databases. We stated earlier that we wouldn’t bump to Go 1.18 until July 1, 2022. This TAS release with Diego 2.64.0 breaks that promise. We apologize. We are rolling back to Diego 2.62.0. If you already successfully deployed to this TAS release with Diego 2.64.0, then you are safe to continue using it.

• Bump diego to version 2.64.0
• Bump garden-runc to version 1.20.6
• Bump loggregator-agent to version 6.0.10
• Bump metrics-discovery to version 3.0.13

2.10.24

Release Date: 04/20/2022

• Bump diego to version 2.62.0
• Bump hwc-offline-buildpack to version 3.1.24
• Bump metrics-discovery to version 3.0.10
• Bump winc to version 2.5.0

  - fix bug with large messages (#22)
  - bump-golang to v0.100.0(now 1.18)
          

2.10.23

Release Date: 03/31/2022

• Bump diego to version 2.61.0
• Bump garden-runc to version 1.20.3
• Bump hwc-offline-buildpack to version 3.1.23
• Bump loggregator-agent to version 6.0.9
• Bump metrics-discovery to version 3.0.9
• Bump windowsfs-release to version 2.35.0

2.10.22

Release Date: 02/28/2022

• [Feature Improvement] Per Golang 1.17’s new and stricter IP parsing standards, any IP addrs with leading zeros in any octets will result in a BOSH template failure to allow operators to remove the leading zeros and try again (affects properties fed into diego-release, garden-runc-release, winc-release, nats-release, and routing-release),.
• [Bug Fix] Smoke tests support for TLSv1.3 only option
• Bump diego to version 2.58.1
• Bump envoy-nginx to version 0.9.0
• Bump garden-runc to version 1.20.0
• Bump hwc-offline-buildpack to version 3.1.22
• Bump loggregator-agent to version 6.0.8
• Bump smoke-tests to version 4.5.0

2.10.21

Release Date: 02/08/2022

• [Security Fix] Diego - Bump containerd to v1.5.9 to fix CVE-2021-43816
• [Feature Improvement] TAS for VMs [Windows] supports compiled releases
• [Feature Improvement] Golang v1.17 contains stricter IP parsing standards, so syslog drains registered using user-provided services cannot contain IP addresses with leading zeros in any octets.
• [Bug Fix] windowsfs-release compilation issue - Cannot extract through symlink
• Bump diego to version 2.57.0
• Bump hwc-offline-buildpack to version 3.1.21
• Bump loggregator-agent to version 6.0.7
• Bump metrics-discovery to version 3.0.7
• Bump smoke-tests to version 4.4.0
• Bump windowsfs-release to version 2.33.2

2.10.20 - Withdrawn

Warning: This release has been removed from VMware Tanzu Network due to a regression in Windows FS Injector 0.21.0.

Release Date: 12/15/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] Diego - Envoy v1.19 uses the original TCP connection pool so that it can accept more than 1024 downstream connections
• [Bug Fix] Smoke Tests uses specified domain for Isolation Segments
• Bump diego to version 2.54.0
• Bump metrics-discovery to version 3.0.7
• Bump smoke-tests to version 4.3.1

2.10.19

Release Date: 11/23/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump diego to version 2.53.1
• Bump hwc-offline-buildpack to version 3.1.20
• Bump windowsfs-release to version 2.31.0

2.10.18

Release Date: 10/20/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• No BOSH release bumps

2.10.17

Release Date: 09/29/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Security Fix] Fixes an issue where BBS socket connections could be kept alive unnecessarily
• [Feature Improvement] Disable Diego container proxy ALPN
• Bump diego to version 2.53.0

2.10.16

Release Date: 09/16/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] garden-runc - Fix handling reserved space on ext4 and generating bundle mounts when SMB volumes are present
• Bump garden-runc to version 1.19.30
• Bump windowsfs-release to version 2.29.0

2.10.15

Release Date: 09/09/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] garden-runc - recover after cell restarts
• Bump garden-runc to version 1.19.29
• Bump windowsfs-release to version 2.28.0

2.10.14

Release Date: 07/15/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump garden-runc to version 1.19.28
• Bump hwc-offline-buildpack to version 3.1.18
• Bump windowsfs-release to version 2.27.0

2.10.13

Release Date: 06/22/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Security Fix] Bump some dependencies to resolve security vulnerabilities
• Bump loggregator-agent to version 6.0.6
• Bump metrics-discovery to version 3.0.6
• Bump windowsfs-release to version 2.26.0

2.10.12

Release Date: 05/27/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• See Known Issues.
• [Feature Improvement] Patch versions can be upgraded without a stemcell upgrade
• [Bug Fix] Smoke Test allows the operator to provide the apps_domain property when deploying TAS and also properly configures user provided space when deploying an isolation segment
• Bump diego to version 2.50.0
• Bump garden-runc to version 1.19.25
• Bump smoke-tests to version 4.3.0
• Bump windowsfs-release to version 2.25.0

2.10.11

Release Date: 03/31/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump windows2019 stemcell to version 2019.32
• Bump windowsfs-release to version 2.23.0

2.10.10

Release Date: 02/19/2021

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump windows2019 stemcell to version 2019.30
• Bump windowsfs-release to version 2.22.0

2.10.9

Release Date: 12/18/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Security Fix] Bump garden-runc-release to address CVE-2020-15257
• Bump windows2019 stemcell to version 2019.29
• Bump garden-runc to version 1.19.18
• Bump windowsfs-release to version 2.20.0

2.10.8

Release Date: 11/18/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• No BOSH release bumps

2.10.7

Release Date: 11/04/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump metrics-discovery to version 3.0.3

2.10.6

Release Date: 10/26/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] Loggregator Agent Release - Prom Scraper metrics server names match
• Bump windows2019 stemcell to version 2019.27
• Bump windowsfs-release to version 2.19.0

2.10.5

Release Date: 10/09/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Feature] The v7 cf CLI is the default CLI
• [Bug Fix] Remove “power_of_two” constraint from CPU resource definitions
• Bump windows2019 stemcell to version 2019.26
• Bump windowsfs-release to version 2.18.0

2.10.4

Release Date: 09/21/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• No BOSH release bumps

2.10.3

Release Date: 09/09/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• Bump windows2019 stemcell to version 2019.25
• Bump diego to version 2.48.0
• Bump envoy-nginx to version 0.7.0
• Bump smoke-tests to version 2.2.0
• Bump windowsfs-release to version 2.17.0

2.10.2

Release Date: 08/24/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] Bump garden-runc to v1.19.16
• Bump garden-runc to version 1.19.16

2.10.1

Release Date: 08/08/2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Bug Fix] System Metrics Scraper/Prom Scraper — Fixes a bug that causes excess log volume and increases scrape interval to reduce metric volume
• Bump windows2019 stemcell to version 2019.24
• Bump garden-runc to version 1.19.14
• Bump windowsfs-release to version 2.16.0

2.10.0

Release Date: July 31, 2020

Note: Windows stemcells v2019.44 and later are not compatible with this version of TAS for VMs [Windows]. You must use a Windows stemcell version between v2019.0 and v2019.43 to install this release.

• [Feature] Support Maestro’s rotation capability by adding Services TLS CA to all app containers
• [Feature] Optionally Converge on Human Readable Timestamps for TAS Component Logs
• [Feature] Make app log rate limit configurable
• [Feature Improvement] Removes metrics by default in aggregate drains
• [Feature Improvement] NATS TLS server runs alongside NATS server
• [Bug Fix] Remove invalid characters in hostnames in outgoing application syslog messages to comply with RFC 5424
• [Bug Fix] Loggregator Agent - Fix certificate issues for all agent metrics
• [Bug Fix] Migrate services/intermediate_tls_ca to /services/tls_leaf for Maestro
• [Bug Fix] Fix server_name value to use Common Name as metrics_agent_metrics_tls
• Add new release smoke-tests at version 2.0.6
• Removed cf-windows-smoke-tests release
• Bump windows2019 stemcell to version 2019.23
• Bump windowsfs-release to version 2.15.0
• Bump windows-utilities to version 0.14.0
• Bump winc to version 2.1.0
• Bump garden-runc to version 1.19.11
• Bump diego to version 2.47.0
• Bump loggregator-agent to version 6.0.2
• Bump metrics-discovery to version 3.0.1

How to Upgrade

The TAS for VMs [Windows] v2.10 tile is available with the release of Ops Manager v2.10. To use the TAS for VMs [Windows] v2.10 tile, you must install VMware Tanzu Operations Manager v2.10 or later and VMware Tanzu Application Service for VMs (TAS for VMs) v2.10 or later.

New Features in TAS for VMs [Windows] v2.10

TAS for VMs [Windows] v2.10 includes the following major features:

Route Emitters Communicate with NATS Over TLS

Route Emitters for Windows Diego Cells send messages to NATS over TLS. This allows your TAS for VMs [Windows] deployment to meet security compliance requirements while relying less on security policy exceptions or add-ons. TLS encryption from Route Emitters to NATS cannot be disabled.

For more information about Route Emitters and TLS encryption, see TLS to Apps and Other Back End Services in HTTP Routing.

Aggregate Syslog Drains Contain Logs Only

When you configure an aggregate syslog drain in TAS for VMs v2.10, by default you receive logs only. You do not also receive metrics. By not including metrics alongside logs, your syslog drain uses fewer resources and reduces network traffic between TAS for VMs components and your external logging service.

If you want the aggregate drain to send metrics along with logs, you can modify your drain URLs.

To continue to see metrics in your drains after upgrading to TAS for VMs v2.10:

1. Navigate to the Ops Manager Installation Dashboard.
2. Click the VMware Tanzu Application Service for VMs tile in the Installation Dashboard.
3. Select System Logging.
4. For Address, enter the hostname or IP address of the syslog server and append ?include-metrics-deprecated=true. For example, https://syslog-server.com:123?include-metrics-deprecated=true.
5. Click Save.

For more information about configuring aggregate syslog drains, see Configure System Logging in Configuring TAS for VMs.

Send Only App Metrics to Firehose

You can choose to prevent the Loggregator Firehose from emitting app logs but still allow the Firehose to emit app metrics. Disabling logs in the Firehose helps reduce the load on TAS for VMs [Windows] by allowing you to scale down Doppler and Traffic Controller VMs.

To configure the Firehose to receive only app metrics, you must select the Disable logs in Firehose, Log Cache syslog ingestion, Enable V1 Firehose, and Enable V2 Firehose checkboxes in the System Logging pane of the TAS for VMs tile. You must also configure Aggregate log and metric drain destinations in the System Logging pane of the TAS for VMs tile. For more information, see Configure System Logging in Configuring TAS for VMs.

Optionally Use Human-Readable Timestamps for Component Logs

TAS for VMs v2.10 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:

• 2019-11-21T22:16:18.750673404Z
• 2019-11-21T22:16:18.750000000Z

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.10.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: 

Components not listed in the table above either do not support RFC3339 timestamps in TAS for VMs v2.10.0 or were already using the RFC3339 timestamp format. Selecting Converge to human-readable RFC3339 format ensures that any additional components that add support for RFC3339 timestamps in later releases of TAS for VMs v2.10 are automatically configured to use RFC3339 timestamps after you upgrade.

To confirm which TAS for VMs components use RFC3339 timestamps:

1. Go to the debug/files endpoint at https://OPS-MANAGER-FQDN/debug/files, where OPS-MANAGER-FQDN is the fully-qualified domain name of your Ops Manager instance.

2. For each component, confirm that the logging.format.timestamp property is set to rfc3339.

Breaking Change: 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.10, 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 in Ops Manager and Runtime Breaking Changes.

Breaking Changes

There are no breaking changes in TAS for VMs [Windows] v2.10.

Known Issues

See the following TAS for VMs [Windows] v2.10 known issues:

Upgrades Fail When the Stemcell Does Not Change

If you upgrade to a version of TAS for VMs [Windows] that uses the same stemcell, TAS for VMs [Windows] can fail to create containers, causing the deployment to fail. If there are stemcell changes or if the Microsoft base layer changes, this error is unlikely to occur.

For more information, see Failure to create containers when upgrading with shared Microsoft base image in the VMware Tanzu Knowledge Base.

Smoke Tests Fail when Isolation Segment in Foundation

The Smoke Test errand runs extra, failing tests when TAS for VMs [Windows] is deployed with Isolation Segment. They are “Compute isolation disabled” and “Application Workflow Linux Applications”.

To work around this issue, disable Smoke Tests. For more information, see Windows Tile smoke-tests fails for isolation segment segments in the VMware Tanzu Knowledge Base.

Windows Stemcell v2019.44 is Incompatible with winfs2019-release v2.33.1 and Earlier

Windows stemcells v2019.44 and later include a newer version of tar that is incompatible with winfs2019-release v2.33.1 and earlier. TAS for VMs [Windows] deployments that use Windows stemcells v2019.44 and later cannot untar winfs2019-release v2.33.1 and earlier. Compatible Windows stemcells for this winfs2019-release include v2019.0 through v2019.43.