cloudfoundry/diego-release v1.34.0

Diego v1.34.0

on GitHub

Changes from v1.33.0 to v1.34.0

• Verified with garden-runc-release v1.11.0.
• Verified with garden-windows-bosh-release v0.13.0.
• Verified with etcd-release v117.
• Verified with cf-mysql-release v35.
• Verified with cflinuxfs2-release v1.185.0.

Significant changes

cfdot

• As a Diego operator, I expect to be able to opt cfdot into setting a request timeout on non-streaming requests to the BBS so that I do not exhaust system resources (in flight)

Custom CAs

• As a Diego deployer, I expect that each separate CA certificate included in containers.trusted_ca_certificates will be placed in a separate file so that I can support applications that do not consume concatenated certs

Routing

• Operator can discover metrics on the latency of gorouter routing table convergence (in flight)

De-Consuling Locks

• As a CF operator, I expect to be able to operate the global-mode route-emitter with either a joint or a pure-Locket lock so that I can remove the dependency on Consul without operating the route-emitters in cell-local mode

Volume Support

• Clean up CSI repos
• Straighten out CSI configuration in the executor
• csibroker and volman check supported versions when connecting to CSI plugins
• local-controller-plugin and local-node-plugin support the csi Identity service
• csi-volume-plugin consumes id and attributes values from service binding mount config

Per-Instance Proxy (Experimental)

• As a Diego operator, I expect to configure the Envoy container proxies dynamically via filesystem updates instead of via the LDS server so that I can avoid its increase in system memory overhead

Docker Support

• dockerapplifecycle should work with azure docker registries

Test Suites and Tooling

• As a Diego contributor, I expect to be able to run the v1.0.0 vizzini test suite against a locally deployed Diego with different combinations of v1.0.0 and latest components
• As a Diego contributor, I expect to be able to verify continuity of application uptime and routability during an upgrade from Diego v1.25.2 to the latest version

BOSH job changes

None.

BOSH property changes

rep and rep_windows

• Added diego.executor.volman.csi_paths.
• Added diego.executor.volman.csi_mount_root_dir.
• Changed containers.proxy.additional_memory_allocation_mb default from 18 to 5.

route_emitter and route_emitter_windows

• Added locks.consul.enabled: Whether the route-emitter in global mode uses Consul for its component lock. Defaults to true.
• Added locks.locket.enabled: Whether the route-emitter in global mode uses Locket for its component lock. Defaults to false.
• Added locks.locket.hostname: Hostname of the Locket service. Defaults to locket.service.cf.internal.
• Added locks.locket.enabled: Port of the Locket service. Defaults to 8891.

BOSH link changes

None.