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

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.

Releases

2.10.4

Release Date: 09/21/2020

  • No BOSH release bumps
Component Version
windows2019 stemcell2019.25
diego2.48.0
envoy-nginx0.7.0
event-log0.9.0
garden-runc1.19.16
hwc-offline-buildpack3.1.13
loggregator-agent6.0.2
metrics-discovery3.0.1
smoke-tests2.2.0
winc2.1.0
windows-utilities0.14.0
windowsfs-release2.17.0

2.10.3

Release Date: 09/09/2020

  • 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
Component Version
windows2019 stemcell2019.25
diego2.48.0
envoy-nginx0.7.0
event-log0.9.0
garden-runc1.19.16
hwc-offline-buildpack3.1.13
loggregator-agent6.0.2
metrics-discovery3.0.1
smoke-tests2.2.0
winc2.1.0
windows-utilities0.14.0
windowsfs-release2.17.0

2.10.2

Release Date: 08/24/2020

  • [Bug Fix] Bump garden-runc to v1.19.16
  • Bump garden-runc to version 1.19.16
Component Version
windows2019 stemcell2019.24
diego2.47.0
envoy-nginx0.6.0
event-log0.9.0
garden-runc1.19.16
hwc-offline-buildpack3.1.13
license
loggregator-agent6.0.2
metrics-discovery3.0.1
smoke-tests2.0.6
winc2.1.0
windows-utilities0.14.0
windowsfs-release2.16.0

2.10.1

Release Date: 08/08/2020

  • [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
Component Version
windows2019 stemcell2019.24
diego2.47.0
envoy-nginx0.6.0
event-log0.9.0
garden-runc1.19.14
hwc-offline-buildpack3.1.13
loggregator-agent6.0.2
metrics-discovery3.0.1
smoke-tests2.0.6
winc2.1.0
windows-utilities0.14.0
windowsfs-release2.16.0

2.10.0

Release Date: July 31, 2020

  • [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
Component Version
windows2019 stemcell2019.23
diego2.47.0
envoy-nginx0.6.0
event-log0.9.0
garden-runc1.19.11
hwc-offline-buildpack3.1.13
loggregator-agent6.0.2
metrics-discovery3.0.1
smoke-tests2.0.6
winc2.1.0
windows-utilities0.14.0
windowsfs-release2.15.0

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 Ops 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: 

Component Jobs
routing gorouter
silk iptables logger, silk-daemon
diego auctioneer, bbs, file_server, locket, rep, route_emitter, ssh_proxy
garden-runc garden
pxc pxc-mysql, proxy, galera-agent, gra-log-purger
mysql-monitoring mysql-metrics, replication-canary

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

There are currently no known issues in TAS for VMs [Windows] v2.10.