CF Networking Release 2.0.0 does not contain major new features, but does include breaking changes for how the Cloud Foundry container networking system is packaged, versioned and deployed.
The biggest change is that the Silk container networking fabric, which may be swapped out for other CNI-compatible network integrations, is now provided in a dedicated BOSH release, silk-release. That leaves cf-networking-release with only those "core" components (Network Policy API and CNI compatibility layer) that serve as extension points for network integrations. The split is intended to simplify the development and deployment of 3rd party network integrations in Cloud Foundry Application Runtime.
More detail:
- To maintain existing container networking features in Cloud Foundry, operators will need to deploy both cf-networking-release and silk-release. This is a breaking change for operators.
- We've "de-namespaced" many of the BOSH manifest properties and renamed some bosh jobs. For manifest authors, these are breaking changes. See the manifest changelog for details.
- Starting now and going forward, we plan to release both cf-networking-release and silk-release at the same time, with the same version numbers. Operators using silk-release should plan to deploy both releases together; we won't support mixed-version deployments.
- We continue to provide upgrade guarantees from cf-networking-release 1.x to the 2.x versions.
- To deploy these releases with cf-deployment, we recommend using the
use-cf-networking-2.ymlexperimental ops-file. Longer term, we're intending for the 2.x versions to become default in CF Deployment.
Silk will no longer be the default cni plugin. To continue using it, you will have to set the following properties in your bosh manifest for the garden-cni job:
cni_plugin_dir: /var/vcap/packages/silk-cni/bin
cni_config_dir: /var/vcap/jobs/silk-cni/config/cni
Be sure to read the manifest changelog for CF Networking Release and the manifest changelog for Silk Release for details about all manifest changes that this release contains.
As always, we welcome your questions and feedback in our Cloud Foundry Slack channel #container-networking or in reply to this message.
Features
- cf-networking-release no longer includes swappable components
- ASGs are applied to multiple interfaces
- cf-networking-release has de-namespaced spec properties
- Audit and fix database timeout configuration for cf-networking
- CF Networking Release and Silk Release have the same version numbers
- Rename cni job to silk-cni in silk-release
Bug Fix
Manifest Changes
There are a lot of manifest changes, you can see them all at the manifest changelog.
Tested with silk-release v2.0.0