0.24.0

This release allows operators to configure the UDP port used for the VXLAN devices and makes it possible to change the IP address range allocated for the container network.

In addition, it adds further improvements to the control scripts for all BOSH jobs and introduces basic uptime monitoring for the silk-daemon.

We do not recommend using cf-networking-release in production yet, but give it a try and give us your feedback in the #container-networking channel on cloudfoundry.slack.com.

Take a look at known issues for current limitations and known issues. Verified with the following:

• CF deployment

Manifest Changes

New Properties

• The host port for receiving VXLAN packets is now configurable as cf_networking.vtep_port for flannel and silk. Overriding this value is optional.

Significant Changes

BOSH configuration

• As an operator I can change the overlay network mask to enlarge the network
• CF networking jobs use links for database configuration
• An operator can override the UDP port used for VXLAN traffic

BOSH job control scripts

• All control scripts are using a common pid_utils
• Fix monit issues with silk-daemon

Silk metrics

• silk-daemon emits an uptime metric

Other

• Explore using context in policy server
• Smoke tests continue to pass during deploys