0.12.0

Key changes include configurable subnet ranges and masks, self service policy configuration and enhancements for reducing policy enforce time.

We do not recommend using netman-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

Deployment Changes

• The subnet and mask for the overlay network is configurable
• As an operator I would like to support more than 254 cells with legacy networking features

Space Developer self-service policy configuration

• Space developers with network.write scope can create policies using the API for apps in spaces they own
• Space developers with network.write scope can delete policies for apps in spaces they own

UX changes

• Remove old delete API endpoint

Performance and Scalability

• As an operator I don't expect iptables to be rewritten continuously when there are no policy changes

Miscellaneous Changes

• The eureka demo example uses the CF_INSTANCE_INTERNAL_IP environment variable
• Compare ingress networking performance with and without netman