0.17.0

This release reduces the Flannel subnet lease renewal interval to alleviate the effects of etcd failures. It also includes a manifest change. Take a look at the manifest change log for details.

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

Significant Changes

Flannel

• Document risks and mitigations for container networking when etcd disappears and comes back with an empty data dir
• Flannel subnet range for a cell should be configurable

Scalability

• Policy server flakes when trying to add/delete several thousand policies
• As an operator I have metrics to help evaluate policy server performance
• As a space developer, I expect list policies to work when there are a lot of policies/apps
• Our docs include recommendations on scaling policy server instances and DB
• When policies are requested by ID, policy server does not query database for all policies

Chores

• Migrate pickelhelm to GCP
• Integrate CNI master and provide feedback to the CNI maintainers