cloudfoundry/diego-release v2.35.0

Diego v2.35.0

on GitHub

Resources

• Download release v2.35.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 89a2bf0bdf53c9a862ac489ec361215bb8e40ce6.

Changes from v2.34.0 to v2.35.0

Significant changes

Component Coordination

• cloudfoundry/diego-release #432: rep prestart hook failed: /proc/sys/net/netfilter/nf_conntrack_max: No such file or directory
  • Previously we relied on pre-start scripts from other jobs to load the nf_conntrack linux module.
    Now we enable nf_conntrack module to assure its available before we update its value.

Routing

• As a CF operator, when I enable route integrity (on Windows and Linux) I expect that when I update my cells with a new compiled package, the update completes successfully within a reasonable amount of time

Per-Instance Proxy

• Envoy proxy binary bumped to c0a1ded969095e2989bac70f0f4637ed4c42ffb1

Test Suites and Tooling

• As a Diego contributor, I expect to be able to configure the vizzini errand with a preloaded rootfs that is included in my Diego deployment so that I do not need to change the code in diego-release to run vizzini against environments with different configurations
• Investigate bbs migrations tests data race

Security

• As a CF operator, I expect that cloud controller generates https urls to file-server assets via a BOSH link from the file-server so I can be sure communication paths in my foundation are secure
• cloudfoundry/locket #9: Cert expiry or misconfiguration can cause useless error messages

Miscellany

• cloudfoundry/bytefmt #23: Add support for Petabyte and Exabyte
• Add deprecation notice for cfhttp v1 package

BOSH property changes

file_server

+ https_url:
+ description: "The URL provided in file_server link"
+ default: "https://file-server.service.cf.internal:8443"

vizzini

+ default_rootfs:
+ description: "Default preloaded rootfs to target for running Tasks and LRPs"
+ default: "preloaded:cflinuxfs3"