Isolation Segment v2.10 Release Notes
This topic contains release notes for Isolation Segment v2.10.
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
- Bump cf-networking to version
- Bump cflinuxfs3 to version
- Bump garden-runc to version
- Bump silk to version
Release Date: July 31, 2020
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.
To install Isolation Segment v2.10, see Installing Isolation Segment.
To install Isolation Segment v2.10, you must first install Ops Manager v2.10.
Isolation Segment v2.10 includes the following major features:
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:
- Navigate to the Ops Manager Installation Dashboard.
- Click the Isolation Segment tile in the Installation Dashboard.
- Select System Logging.
- For Address, enter the hostname or IP address of the syslog server and append
?include-metrics-deprecated=true. For example,
- Click Save.
For more information about configuring aggregate syslog drains, see Configure System Logging in Configuring TAS for VMs.
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.
There are no known issues for Isolation Segment v2.10 at this time.