[cf-dev] CF Container Networking 2.0!

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[cf-dev] CF Container Networking 2.0!

Amelia Downs

Hello all,


The CF Container Networking team has released cf-networking-release 2.0.0 and silk-release 2.0.0.


The releases do not contain major new features, but do 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.  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.

  • 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.yml experimental ops-file.  Longer term, we're intending for the 2.x versions to become default in cf-deployment.


For details, look at our release notes for cf-networking-release and silk-release.  If you have a non-standard BOSH manifest, be sure to read the cf-networking-release manifest changelog and silk-release manifest changelog.


As always, we welcome your questions and feedback in our Slack channel #container-networking or in reply to this message.


Try it out!

These new releases will be included by default in cf-deployment 2.0. Until then, you can use the opsfile cf-deployment/operations/experimental/use-cf-networking-2.yml


We have also duplicated and fixed other affected opsfiles, and suffixed them with ‘with-networking-2.yml’.


Best,

The CF Container Networking Team



_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#7998) | [hidden email] | [hidden email] | Mute This Topic | New Topic

Change Your Subscription
Group Home
[hidden email]
Terms Of Service
Unsubscribe From This Group

_._,_._,_
Reply | Threaded
Open this post in threaded view
|

Re: [cf-dev] CF Container Networking 2.0!

Shannon Coen
Kudos to the Networking team!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Fri, May 11, 2018 at 11:11 AM, Amelia Downs <[hidden email]> wrote:

Hello all,


The CF Container Networking team has released cf-networking-release 2.0.0 and silk-release 2.0.0.


The releases do not contain major new features, but do 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.  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.

  • 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.yml experimental ops-file.  Longer term, we're intending for the 2.x versions to become default in cf-deployment.


For details, look at our release notes for cf-networking-release and silk-release.  If you have a non-standard BOSH manifest, be sure to read the cf-networking-release manifest changelog and silk-release manifest changelog.


As always, we welcome your questions and feedback in our Slack channel #container-networking or in reply to this message.


Try it out!

These new releases will be included by default in cf-deployment 2.0. Until then, you can use the opsfile cf-deployment/operations/experimental/use-cf-networking-2.yml


We have also duplicated and fixed other affected opsfiles, and suffixed them with ‘with-networking-2.yml’.


Best,

The CF Container Networking Team




_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#7999) | [hidden email] | [hidden email] | Mute This Topic | New Topic

Change Your Subscription
Group Home
[hidden email]
Terms Of Service
Unsubscribe From This Group

_._,_._,_