Isolation Segment v2.10 Release Notes

Page last updated:

This topic contains release notes for Isolation Segment v2.10.

Releases

2.10.11

Release Date: 03/31/2021

• [Breaking Change] This restores the breaking change originally found in 2.10.9 and temporarily remediated in 2.10.10: Gorouter update to Golang v1.15 introduces stricter transfer-encoding header standards. Stricter header standards break Spring apps that incorrectly set the header. For more information, see Applications on TAS for VMs get 502 chunked response error in the Knowledge Base.
• [Feature] gorouter - Operator can limit CAs gorouter trusts when validating client certs to a specified list
• Bump ubuntu-xenial stemcell to version 621.115
• Bump cflinuxfs3 to version 0.227.0
• Bump diego to version 2.49.0
• Bump routing to version 0.212.0

2.10.10

Release Date: 02/19/2021

• [Temporary Remediation] Gorouter - Emit log, emit metric, and don’t error when an app response contains a duplicate “Transfer-Encoding: chunked” header. This is a stop gap to discover which apps are sending invalid responses. For more information, see Applications on TAS for VMs get 502 chunked response error in the Knowledge Base.
• Bump ubuntu-xenial stemcell to version 621.101
• Bump cflinuxfs3 to version 0.223.0
• Bump routing to version 0.211.1

2.10.9

Release Date: 12/18/2020

• [Breaking Change] Gorouter update to Golang v1.15 introduces stricter transfer-encoding header standards. Stricter header standards break Spring apps that incorrectly set the header. For more information, see Applications on TAS for VMs get 502 chunked response error in the Knowledge Base.
• [Security Fix] Bump garden-runc-release to address CVE-2020-15257
• Bump ubuntu-xenial stemcell to version 621.94
• Bump cf-networking to version 2.35.0
• Bump cflinuxfs3 to version 0.216.0
• Bump garden-runc to version 1.19.18
• Bump routing to version 0.210.0
• Bump silk to version 2.35.0

2.10.8

Release Date: 11/18/2020

• No BOSH release bumps

2.10.7

Release Date: 11/04/2020

• [Bug Fix] Downgrade haproxy to prevent blackbox failure
• Bump ubuntu-xenial stemcell to version 621.90
• Bump metrics-discovery to version 3.0.3

2.10.6

Release Date: 10/26/2020

• [Feature Improvement] Networking: Clarify that drain timeout should be lower than backend request timeout to reduce drain time during deploys
• [Bug Fix] Loggregator Agent Release - Prom Scraper metrics server names match
• Bump ubuntu-xenial stemcell to version 621.89
• Bump cf-networking to version 2.34.0
• Bump cflinuxfs3 to version 0.210.0
• Bump routing to version 0.208.0
• Bump silk to version 2.34.0

2.10.5

Release Date: 10/09/2020

• [Feature] The v7 cf CLI is the default CLI
• [Bug Fix] Remove “power_of_two” constraint from CPU resource definitions
• [BUG FIX] syslog-agent - Add ops man cert to use syslog ingestion for log-cache
• Bump ubuntu-xenial stemcell to version 621.85
• Bump cflinuxfs3 to version 0.208.0

2.10.4

Release Date: 09/21/2020

• Bump ubuntu-xenial stemcell to version 621.84
• Bump cflinuxfs3 to version 0.204.0
• Bump routing to version 0.207.0

2.10.3

Release Date: 09/09/2020

• [Security Fix] Fix for CVE-2020-5420: Improve Gorouter’s handling of invalid HTTP responses
• [Feature Improvement] Gorouter aliases /healthz to /health in order to prevent downtime during upgrades
• Bump ubuntu-xenial stemcell to version 621.82
• Bump cf-networking to version 2.33.0
• Bump diego to version 2.48.0
• Bump nfs-volume to version 7.0.4
• Bump routing to version 0.206.0
• Bump silk to version 2.33.0
• Bump smoke-tests to version 2.2.0

2.10.2

Release Date: 08/24/2020

• [Bug Fix] loggr-syslog-agent - Fix server alternative name
• [Bug Fix]: Return 502 TLS Handshake error for an unresponsive backend
• [Bug Fix] Bump garden-runc to v1.19.16
• Bump ubuntu-xenial stemcell to version 621.78
• Bump cflinuxfs3 to version 0.203.0
• Bump garden-runc to version 1.19.16
• Bump routing to version 0.205.0

2.10.1

Release Date: 08/08/2020

• [Bug Fix] Fix issue where requests to internal routes could fail due to incorrect case-sensitivity in DNS lookup in the service discovery controller.
• [Bug Fix] System Metrics Scraper/Prom Scraper — Fixes a bug that causes excess log volume and increases scrape interval to reduce metric volume
• Bump ubuntu-xenial stemcell to version 621.77
• Bump cf-networking to version 2.31.0
• Bump cflinuxfs3 to version 0.202.0
• Bump garden-runc to version 1.19.14
• Bump silk to version 2.31.0

2.10.0

Release Date: July 31, 2020

• See New Features in Isolation Segment v2.10
• See Breaking Changes

About Isolation Segment

The Isolation Segment v2.10 tile is available for installation with Ops Manager v2.10.

Isolation segments provide dedicated pools of resources where you can deploy apps and isolate workloads. Using isolation segments separates app resources as completely as if they were in different Ops Manager deployments but avoids redundant management and network complexity. For more information about isolation segments, see Isolation Segments in TAS for VMs Security.

For more information about using isolation segments in your deployment, see Managing Isolation Segments.

How to Install

To install Isolation Segment v2.10, see Installing Isolation Segment.

To install Isolation Segment v2.10, you must first install Ops Manager v2.10.

New Features in Isolation Segment v2.10

Isolation Segment v2.10 includes the following major features:

Aggregate Syslog Drains Contain Logs Only

When you configure an aggregate syslog drain in Isolation Segment 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 Isolation Segment v2.10:

1. Navigate to the Ops Manager Installation Dashboard.
2. Click the Isolation Segment 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.

Configurable Sticky Session Cookie Names

You can supply sticky session cookie names for the Gorouter to use when handling sticky sessions. The Gorouter uses these cookies to support session affinity, or sticky sessions. For more information, see Session Affinity in HTTP Routing.

By default, the Gorouter uses JSESSIONID. Some apps require a different session name. For example, Spring WebFlux requires SESSION for the session cookie name.

To supply cookie names, see Configure Networking in Installing Isolation Segment.

Breaking Changes

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

Known Issues

There are no known issues for Isolation Segment v2.10 at this time.