2.4.0

This release has no major changes.
Tested with cf-networking-release v2.4.0

2.3.0

This release includes the following new features:

• Bandwidth limiting is supported through CNI chaining
• Fixes to database and Consul timeout configurations

Tested with cf-networking-release v2.3.0

Significant Changes

Manifest Changes

New Properties

• An optional parameter has been added to the silk-controller job to configure the consul dns health check timeout. Defaults
  to 5 seconds.
  • health_check_timeout_seconds

Changed Properties

• Namespaced the connect_timeout_seconds under database in the silk-controller job.
  • health_check_timeout_seconds

CNI enhancements

• Silk release should provide bandwidth shaping via chaining to upstream CNI plugin
• CNI Wrapper integration tests should pass from Docker for Mac

Timeout changes

• Consul DNS healthcheck timeout should be independently configurable from the database connection timeout
• cloudfoundry/silk #4: Too many open connections error

Router on the overlay

• Silk Controller supports CRUD for a Single IP Lease
• Silk daemon can acquire and connect a Single IP
• Silk-connected VMs can connect to App Ports

Chores

• Create known issues doc for silk-release

2.2.0

With this release silk controller and policy server can connect to mySQL database with TLS.

Tested with cf-networking-release v2.2.0

Significant Changes

• Silk controller can connect to MySQL with TLS
• Network policy server can connect to MySQL with TLS
• do we need to downgrade to Go 1.9?

2.1.0

Features

• A process inside the app container can connect to the cell-local service
• Consul DNS healthcheck timeout should be hardcoded back to 5 seconds

Bug

• iptables logging should work correctly with recent versions of syslog release

Manifest Changes

• An optional parameter host_tcp_services has been added to the silk-cni job to specify TCP addresses running on the BOSH VM that should be accessible from containers. The address must not be in the 127.0.0.0/8 range. The silk-cni plugin will install an iptables INPUT rule for each service.
• See all manifest changes in the manifest changelog.

---

Tested with cf-networking-release v2.1.0

2.0.0

silk-release packages the Silk container networking fabric for deployment with BOSH in the Cloud Foundry Application Runtime. It is designed to work with CF Networking Release v2.0.0. See those release notes for a summary of how they work together.

Features

• An operator can disable silk-release
• Rename cni job to silk-cni in silk-release
• CF Networking Release and Silk Release have the same version numbers

Bug Fix

• cloudfoundry/cf-networking-release #37: Request's source IP is a cell's IP instead of a VXLAN one.

Manifest Changes

• You can see all of the changes in the manifest changelog

Tested with cf-networking-release v2.0.0

0.3.0

• ASGs are applied to multiple interfaces
• Update to go 1.10
• use cloudfoundry/filelock repo
• Tested with cf-networking-release v1.13.0

0.2.0

• cf-networking-release no longer includes swappable components
• An operator can configure a BOSH property to indicate which interface name to use for VXLAN traffic
• Update cf-networking-release and silk-release db timeout connection defaults
• Validation for BOSH property to configure VXLAN interface
• Underlay network can be specified in job properties by bosh network name
• switch pipelines to use silk-release opsfiles from cf-d
• Tested with cf-networking-release v1.12.0

0.1.0

• Create silk-release with swappable parts of cf-networking-release
• silk-release is on bosh.io
• An operator can configure a BOSH property to indicate which interface to use for VXLAN traffic
• ASGs are applied to multiple interfaces
• Properties in silk-release are not name spaced to cf-networking
• Tested with cf-networking-release v1.11.0