This topic contains release notes for Isolation Segment v3.0.
VMware Tanzu Application Service for VMs (TAS for VMs) is certified by the Cloud Foundry Foundation for 2023.
For more information about the Cloud Foundry Certified Provider Program, see How Do I Become a Certified Provider? on the Cloud Foundry website.
Because VMware uses the Percona Distribution for MySQL, expect a time lag between Oracle releasing a MySQL patch and VMware releasing TAS for VMs containing that patch.
Release Date: 03/21/2023
Note: This version of TAS for VMs contains a known issue with Gorouter error handling for backend app requests. Failures that previously returned HTTP Status Codes 496, 499, 503, 525, or 526 may instead return 502. Additionally, stale routes may fail to be pruned properly, which could result in apps unexpectedly returning HTTP Status Codes 502.
## Changes * Golang: Updated to v1.19.4 (#32) * Golang: Updated to v1.19.5 (#37) * Golang: Updated to v1.19.5 (#44) * Golang: Updated to v1.20.1 (#48) ## Dependencies * **mapfs:** Updated to v`98da9f0`.
## Changes * Golang: Updated to v1.19.4 (#259) * Golang: Updated to v1.19.5 (#279) * Golang: Updated to v1.19.5 (#298) * Simplify submodule names (#278) ## Dependencies * **bosh-template:** Updated to v2.4.0.
## Changes - No changes from last version. - Fixing CI so that artifacts are generated correctly for github release. ## ✨ Built with go 1.20.1 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.258.0...v0.259.0 ## Resources - [Download release v0.259.0 from bosh.io](https://bosh.io/releases/github.com/cloudfoundry/routing-release?version=0.259.0).
## Changes - Update healthchecker to [0.4.0](https://github.com/cloudfoundry/healthchecker-release/releases/tag/v0.4.0) - Increase startup delay default to 30 seconds [PR](https://github.com/cloudfoundry/healthchecker-release/pull/2) - Upgrade golang to 1.20.1 ## Bosh Job Spec changes: ```diff diff --git a/jobs/acceptance_tests/spec b/jobs/acceptance_tests/spec index 65bf4c30..6a73b9ae 100644 --- a/jobs/acceptance_tests/spec +++ b/jobs/acceptance_tests/spec @@ -7,7 +7,7 @@ templates: bpm.yml.erb: config/bpm.yml packages: - - golang-1.19-linux + - golang-1.20-linux - acceptance_tests - rtr - cf-cli-6-linux diff --git a/jobs/smoke_tests/spec b/jobs/smoke_tests/spec index b16357ed..0426dc99 100644 --- a/jobs/smoke_tests/spec +++ b/jobs/smoke_tests/spec @@ -7,7 +7,7 @@ templates: bpm.yml.erb: config/bpm.yml packages: - - golang-1.19-linux + - golang-1.20-linux - acceptance_tests - cf-cli-6-linux ``` ## ✨ Built with go 1.20.1 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.257.0...v0.258.0 ## Resources - [Download release v0.258.0 from bosh.io](https://bosh.io/releases/github.com/cloudfoundry/routing-release?version=0.258.0).
## Changes - Bumped to build with golang 1.19.6 ## ✨ Built with go 1.19.6 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.256.0...v0.257.0 ## Resources - [Download release v0.257.0 from bosh.io](https://bosh.io/releases/github.com/cloudfoundry/routing-release?version=0.257.0).
## Changes * Backfill property tests for force_noserverino (#103) ## Dependencies * **smbbroker:** Updated to v`17e471d`.
* update golang to 1.20.1 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.1.2...v12.1.3###
## What's Changed * update dependencies * upgrade to go 1.20 by @rroberts2222 in https://github.com/cloudfoundry/syslog-release/pull/118 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.1.1...v12.1.2
Release Date: 02/28/2023
## What's Changed * update dependencies * Upgrade to go 1.20.1 by @rroberts2222 in https://github.com/cloudfoundry/loggregator-agent-release/pull/224 **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.7...v6.5.8
* update golang to 1.20.1 **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.6...v3.2.7###
## What's Changed * Upgrade to go 1.20 by @rroberts2222 in https://github.com/cloudfoundry/metrics-discovery-release/pull/104 **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.5...v3.2.6
## What's Changed * Update dependencies * Expire individual metrics by @rroberts2222 in https://github.com/cloudfoundry/metrics-discovery-release/pull/103 **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.4...v3.2.5
## Changes - Update healthchecker in release to stable version ## ✨ Built with go 1.19.5 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.255.0...v0.256.0 ## Resources - [Download release v0.256.0 from bosh.io](https://bosh.io/releases/github.com/cloudfoundry/routing-release?version=0.256.0).
## Changes * Add force_noserverino property in smbdriver job (#102) ## Dependencies * **bosh-template:** Updated to v2.4.0.
## Dependencies * **smbdriver:** Updated to v`6cc617a`.
## Changes * Golang: Updated to v1.19.4 (#76) ## Dependencies * **rspec:** Updated to v3.12.0.
Release Date: 02/09/2023
shbinary in the docker image to execute properly.
## What's Changed * Sanitize ProcID in syslog messages so messages with utf-8 in the source_type are not dropped by @Benjamintf1 in https://github.com/cloudfoundry/loggregator-agent-release/pull/202 * Update dependencies **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.6...v6.5.7
[Upgrade healthchecker in release](https://github.com/cloudfoundry/routing-release/commit/ddb43e9e746b009d0ea6e6cf8cf8e7eb059ffafc). In order to limit the scope of packages brought in with the introduction of http healthchecker, we migrated the healthchecker package out of cf-networking-helpers into its own release. **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.254.0...v0.255.0 ✨ Built with go 1.19.5
Release Date: 01/30/2023
Release Date: 01/16/2023
## What's Changed * fix scraping with non-positive intervals to preserve non-scraping behavior by @Benjamintf1 in https://github.com/cloudfoundry/loggregator-agent-release/pull/174 * updated some dependencies. **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.5...v6.5.6
✨ Built with go 1.19.5 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.253.0...v0.254.0
## What's Changed * Specs to make maxRetries configurable for endpoints and route-services by @domdom82 in https://github.com/cloudfoundry/routing-release/pull/298 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.252.0...v0.253.0
## What's Changed - Improve random source for least connection pool to be thread safe. Thanks Daniel Lynch! **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.251.0...v0.252.0
Port assets/ruby_simple to Ruby 3
Release Date: 12/15/2022
- bump-golang to v0.114.0 for golang 1.19.4 - Bump google.golang.org/grpc from 1.50.1 to 1.51.0 in /src - Bump github.com/valyala/fasthttp from 1.41.0 to 1.43.0 in /src - Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 in /src - Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 in /src - Bump github.com/prometheus/client_model from 0.2.0 to 0.3.0 in /src - Bump golangci/golangci-lint-action from 3.3.0 to 3.3.1
## What's Changed - Bump to go1.19.3 - Bump dependencies **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.3...v6.5.4
## What's Changed * Fix logs for forwarder agent drops by @rroberts2222 in https://github.com/cloudfoundry/loggregator-agent-release/pull/156 **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.2...v6.5.3
## What's Changed * Bump golang to 1.19.2 **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.1...v6.5.2
## What's Changed * remove the use of sha1 by @duanemay in https://github.com/cloudfoundry/loggregator-agent-release/pull/133 * Bump github.com/valyala/fasthttp from 1.39.0 to 1.40.0 in /src by @dependabot in https://github.com/cloudfoundry/loggregator-agent-release/pull/129 * Upgrade ginkgo to v2 by @ctlong in https://github.com/cloudfoundry/loggregator-agent-release/pull/135 * Golang 1.19.1 by @rroberts2222 in https://github.com/cloudfoundry/loggregator-agent-release/pull/138 ## New Contributors * @duanemay made their first contribution in https://github.com/cloudfoundry/loggregator-agent-release/pull/133 * @rroberts2222 made their first contribution in https://github.com/cloudfoundry/loggregator-agent-release/pull/138 **Full Changelog**: https://github.com/cloudfoundry/loggregator-agent-release/compare/v6.5.0...v6.5.1
- bump-golang to v0.114.0 for golang 1.19.4 - Bump github.com/nats-io/nats.go from 1.19.0 to 1.21.0 in /src - Bump google.golang.org/grpc from 1.50.1 to 1.51.0 in /src - Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 in /src - Bump github.com/prometheus/client_golang from 1.13.1 to 1.14.0 in /src - Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 in /src - Bump golangci/golangci-lint-action from 3.3.0 to 3.3.1
## What's Changed * Bump to go1.19.3 * Bump dependencies **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.2...v3.2.3
## What's Changed * update golang to 1.19.2 **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.1...v3.2.2
## What's Changed * Bump github.com/onsi/ginkgo/v2 from 2.1.6 to 2.2.0 in /src by @dependabot in https://github.com/cloudfoundry/metrics-discovery-release/pull/51 * Bump github.com/nats-io/nats.go from 1.16.0 to 1.17.0 in /src by @dependabot in https://github.com/cloudfoundry/metrics-discovery-release/pull/50 * Replace `ioutil` use with `io` and `os` by @ctlong in https://github.com/cloudfoundry/metrics-discovery-release/pull/52 * Bump to golang 1.19.1 by @Benjamintf1 in https://github.com/cloudfoundry/metrics-discovery-release/pull/54 ## New Contributors * @rroberts2222 made their first contribution in https://github.com/cloudfoundry/metrics-discovery-release/pull/55 **Full Changelog**: https://github.com/cloudfoundry/metrics-discovery-release/compare/v3.2.0...v3.2.1
## What's Changed - When the `router.ca_certs` property switched from a multi-line string of certs, to an array of certs, gorouter started failing to start up if any of the certs provided were invalid. Previously they were ignored. This has been reverted, so that any invalid CA certs are ignored during startup. Thanks @ameowlia! **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.250.0...v0.251.0
**Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.249.0...v0.250.0 ## ✨ Built with go 1.19.4
## What's Changed * Switch to healthecker package in cf-networking-helpers by @mariash in https://github.com/cloudfoundry/routing-release/pull/302 * Add healthchecker package to sync-package-specs file by @mariash in https://github.com/cloudfoundry/routing-release/pull/303 * **Potential Breaking Change:** In preperation for mtls between gorouter and routing api, add gorouter backends ca to routing-api. Rendering these certs depends on routing-api consuming a link from gorouter. If you have multiple gorouter instance groups (for example in the case of isolation segments), you will need to rename bosh links to prevent the error "Multiple link providers found. For an example of link renaming, see [this ops file](https://github.com/cloudfoundry/cf-deployment/blob/main/operations/test/add-persistent-isolation-segment-router.yml#L74) by @reneighbor in https://github.com/cloudfoundry/routing-release/pull/300 * Ensure gorouter-healthchecker doesn't restart gorouter forever on failure by @geofffranks in https://github.com/cloudfoundry/routing-release/pull/305 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/0.248.0...v0.249.0
## What's Changed * Handle nil ca cert in ca_certs property list
## What's Changed * gorouter template cleans `router.ca_certs` property to remove empty certificates
## What's Changed * Update `router.ca_certs` property to accept and array of certificates instead of a string block. Thanks @peanball!
## What's Changed * Gorouter's pre-start script now reserves ports used by other CF components when it increases the number of ephemeral ports available via `/proc/sys/net/ipv4/ip_local_reserved_ports`. This resolves issues when components fail to start up during deploys/monit restarts due to accidental port collisions with outbound traffic from the VM. Thanks @ameowlia ! * Routing-release no longer makes use of the deprecated uaa-go-client, and uses go-uaa instead * The `routing_utils/nats_client` helper utility now supports saving + loading gorouter's routing tables! Thanks @domdom82 ! * Fixed a memory leak with `gorouter` that resulted in HTTP request objects being held open if a client canceled the connection before the App responded. Thanks @geofffranks ! * **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.244.0...v0.245.0 ## ✨ Built with go 1.19.3
Create bosh final release 4.8.1
Create bosh final release 4.8.0
## What's Changed * Update golang to 1.19.4 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.1.0...v12.1.1
## What's Changed * allow setting tls library by @rroberts2222 in https://github.com/cloudfoundry/syslog-release/pull/105 ## New Contributors * @acrmp made their first contribution in https://github.com/cloudfoundry/syslog-release/pull/102 * @rroberts2222 made their first contribution in https://github.com/cloudfoundry/syslog-release/pull/105 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.0.6...v12.1.0
## What's Changed * update dependencies * update golang to 1.19.3 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.0.5...v12.0.6
## What's Changed * update to golang 1.19.2 **Full Changelog**: https://github.com/cloudfoundry/syslog-release/compare/v12.0.4...v12.0.5
Release Date: 12/01/2022
Release Date: 11/15/2022
## Changes * Replace `go get` with `go install` (#23) * Update vendored package golang-1-linux (#26) * Update vendored package golang-1-linux (#27) ## Dependencies * **mapfs:** Updated to v`27f8711`.
## Changes * Fix upgrade from 7.1.6 (#253) * Include openldap 2.4.44 blob in release to use it in Xenial (#254)
## Changes * Add final release 7.1.6 [ci skip] * Bump OpenLDAP package to 2.5.13 LTS, which supports xenial (#241) * Remove libnfsidmap from jammy. Was replaced by new nfs-utils (#220) * Replace `go get` with `go install` (#209) ## Dependencies * **bosh-template:** Updated to v2.3.0.
## What's Changed * Emit access logs for 431 responses to Loggegator [gorouter PR #331](https://github.com/cloudfoundry/gorouter/pull/331). Thanks @dsabeti ! * Always suspend pruning when nats is down https://github.com/cloudfoundry/routing-release/pull/287. Thanks @ameowlia ! * **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.243.0...v0.244.0 ## ✨ Built with go 1.19.2
🎉 Bumped to go1.19.2 **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.242.0...v0.243.0
## What's Changed - `tcp_router` is now more verbose when running `haproxy_reloader` to assist in diagnosting failed reloads. Thanks @geofffranks! 🎉 ([PR 9](https://github.com/cloudfoundry/cf-tcp-router/pull/9)) - `gorouter` will now truncate access logs that exceed loggregator + UDP packet limits, so that we no longer drop access log messages sent to the firehose. Thanks @ameowlia @ebroberson! 😻 ([PR 328](https://github.com/cloudfoundry/gorouter/pull/328) and [PR 329](https://github.com/cloudfoundry/gorouter/pull/329)) **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.241.0...v0.242.0 ## ✨ Built with go 1.18 * despite what the docs/go.version says * because the go 1.18 package is present
🎉 ~~Bumped to go1.19.1~~ * Still using go 1.18 * despite what the docs/go.version says * because the go 1.18 package is present * @plowin submitted [gorouter PR 327](https://github.com/cloudfoundry/gorouter/pull/327) to adjust endpoint-not-unregistered log-level to 'info' **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.240.0...v0.241.0
## What's Changed * @geofffranks and @ameowlia added property `router.max_header_bytes` to the gorouter job. * This value controls the maximum number of bytes the gorouter will read parsing the request header's keys and values, including the request line. * It does not limit the size of the request body. * An additional padding of 4096 bytes is added to this value by go. * Requests with larger headers will result in a 431 status code. **Full Changelog**: https://github.com/cloudfoundry/routing-release/compare/v0.239.0...v0.240.0 ## Manifest Property Changes | Job | Property | 0.237.0 | 0.238.0 | | --- | --- | --- | --- | | `gorouter` | `router.max_header_bytes` | didn't exist | 1048576 (1MB) | ## ✨ Built with go 1.18.6
## Changes * Update vendored package golang-1-linux (#67) * Update vendored package golang-1-linux (#70) ## Dependencies * **bosh-template:** Updated to v2.3.0.
Release Date: 10/06/2022
Create bosh final release 4.7.0
To install Isolation Segment v3.0, see Installing Isolation Segment.
To install Isolation Segment v3.0, you must first install Ops Manager v3.0. For more information, see the Ops Manager documentation.
There are no new features for Isolation Segment v3.0.
All VMs that TAS for VMs v3.0 deploys run on the Jammy Jellyfish stemcell described in Jammy Jellyfish Stemcell Support above. Because of this, any add-ons from other tiles or configured in the BOSH Director that are colocated on TAS for VMs VMs do not function unless they support the Jammy Jellyfish stemcell.
Tiles that are compatible TAS for VMs v3.0 already work with Jammy Jellyfish stemcells.
Further, the use of the Jammy Stemcell means TAS now requires an Ops Manager with Jammy support, which means Ops Manager version 2.10.33 or greater.
Isolation Segment v3.0 includes the following breaking changes:
In Isolation Segment v3.0, HAProxy is removed.
If you are upgrading to Isolation Segment v3.0 from Isolation Segment v2.13 or earlier, you must re-configure the following settings in the Isolation Segment tile before you upgrade:
In the Networking pane:
In the Resource Config pane:
For more information about configuring these settings, see Configure Networking and Configure Resources in Installing Isolation Segment.
The global log rate limit that measures app log rates in lines per second is deprecated in favor of per-app log rate limits that measure app log rates in bytes per second.
If you have configured a global log rate limit in lines per second, VMware recommends that you re-configure your apps to use log rate limits in bytes per second.
If you still want to use the global log rate limit, logs that exceed the log rate limit are immediately dropped. Previously, logs that exceeded the log rate limit were buffered and released at the configured log rate.
For more information about app log rate limits, see App Log Rate Limiting.
There are no known issues for Isolation Segment v3.0.