Netman is no more! The key change in this release is a rename from netman to cf-networking. This change is documented in the manifest changelog. At this point, there are no changes to manifest properties other than the release name.
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:
Significant Changes
Manifest Changes
Performance
- Compare c2c networking latency vs. router latency
- As PM I would like a measure of latency to apply a single additional policy with a number of existing policies
- As PM I would like to know how the effect of having a large ASG config on adding a single policy
Troubleshooting
- CF CLI Plugin respects CF_TRACE environment variable
- As a space developer I get a meaningful error message when I don't have network.write scope and try to configure a policy
- Add a Troubleshooting page for CF networking