cloudfoundry/diego-release v2.13.0 on GitHub

Resources

Changes from v2.12.2 to v2.13.0

NOTE: Some of the BOSH jobs in diego-release have set certain Linux kernel parameters automatically depending on whether they detected via their cgroup that they were running inside of a container. The Diego team has observed that this detection process does not work correctly when the jobs run on Xenial-based BOSH stemcells, though. Rather than continue to rely on this cgroup heuristic, the Diego team is altering these jobs to provide a BOSH property to control explicitly whether each job sets these kernel parameters, starting with the rep job in Diego v2.13.0. (The bbs file_server, and locket jobs will follow suit in a forthcoming release.)

The jobs will still default to setting these kernel parameters, so that there is no behavioral change on VM-based BOSH cloud providers. Deployments to containerized cloud providers such as BOSH-Lite may need to opt out of setting these kernel parameters, though. The Diego team has already updated the BOSH-Lite operations file accordingly in the latest cf-deployment manifest via this extra operation.

Significant changes

Xenial Integration

As a CF operator, I expect to be able to opt in or out of the rep job setting kernel parameters so that I can ensure that they are set appropriately on Xenial stemcells

BOSH job changes

None.

BOSH property changes

`rep`

Adds set_kernel_parameters: Whether to set /proc/sys kernel parameters. As discussed above, defaults to true, but on some containerized cloud providers should be set to false.

BOSH link changes