WARNING: DEPLOY 2.15.1 BEFORE UPGRADING TO THIS RELEASE
This release includes migrations that cause cf push downtime while upgrading. The length of this downtime depends on the size of your deployment, and the number of VMs running policy-server-internal. This bug does not affect running apps.
To prevent this bug from happening, you can upgrade to cf-networking-release 2.15.1 first, before upgrading to 2.16.0+. If you upgrade through 2.15.1 you will not encounter this downtime.
This release includes the following features
- Support for dynamic egress policy configuration using a destination object has begun. For more information, read our feature narrative. Note: We no longer support the experimental dynamic egress configuration with in-line destination
- Added defaults for max_open_connections, max_idle_connections and connections_max_lifetime_seconds for policy server and policy server internal.
Tested with silk-release v2.16.0
Significant Changes
Dynamic Egress
- Github: Remove instructions about experimental dynamic egress APIs
- As an operator, I want to add a new destination object in order to configure an egress policy - Happy path
- As an operator, I want to add a new destination object in order to configure an egress policy - No permission
- As an operator with network.admin, I can add an egress policy from an app/space to a destination object - Happy path
- As an operator with network.admin, I can add an egress policy from an app/space to a destination object - No Permission
- Dynamic Egress - Switch ids to guids for destinations
- Dynamic Egress - Switch ids to guids for egress policies