Skip to content

0.18.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@container-networking-bot container-networking-bot released this 14 Mar 23:03
· 3205 commits to develop since this release

Lots of good stuff in this release. Highlights include:

  • Logging for c2c iptables can be enabled through a BOSH property
  • Container networking scales to 20K application instances with 3 policies per application.
  • Initial support for logging ASG iptables through a BOSH property. ASG logs will be prefixed with OK_ or DENY_.
  • If you are running Diego release v1.10.1 you must upgrade to this release

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:

New Manifest Properties

  • cf_networking.rep_listen_addr_admin enables our drain scripts to wait for the Diego rep to exit.
    It should always be the same value as diego.rep.listen_addr_admin. It defaults to 127.0.0.1:1800.
  • cf_networking.garden_external_networker.iptables_asg_logging globally enables iptables logging for
    all ASGs, including logging of denied packets. Defaults to false.
  • cf_networking.vxlan_policy_agent.iptables_c2c_logging enables iptables logging for
    container-to-container traffic. It defaults to false. Note: this is already
    configurable at runtime.
  • cf_networking.plugin.health_check_port allows BOSH to better health-check the flanneld process
    required for connectivity.

Removed Manifest Properties

  • cf_networking.policy_server.database.connection_string was deprecated in v0.10.0 and is now removed.

Significant Changes

Scalability

Upgrades

Manifest Changes

Security

Chores

Stability

Logging

Internal integration