0.23.0

This release improves the interaction between monit and silk-daemon. It also includes improvements to iptables configuration and logging.

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

None

Significant Changes

iptables

• iptables logs leave a space between the container handle and the next field in the log
• Our iptables rules are agnostic to system defaults and lower-priority chains
• Default deny is agnostic to changes in the overlay network range

Policy Server

• VPA and silk-daemon connecting to controllers should have reasonable timeouts

Bug fixes

• When the cf_networking.mtu is not set, it is incorrectly passed through as -50.