cloudfoundry/diego-release v2.3.0

Diego v2.3.0

on GitHub

Changes from v2.2.0 to v2.3.0

• Verified with cloudfoundry/cf-deployment@59fe9d1f04b31d4e03ec252d91d5e2e46e67ee3d.
• Verified with garden-runc-release v1.12.1.
• Verified with garden-windows-bosh-release v0.13.0.
• Verified with cflinuxfs2-release v1.195.0.

Significant changes

cfdot

• cloudfoundry/diego-release #387: cfdot broken on stemcell series 3541

Component Logging and Metrics

• As a CF operator, I expect to be able to opt all the Diego components into the improved lager timestamp format so that I can understand their logs more easily
• BBS should log detected-missing-cells only if it actually detected at least one missing cell

Documentation

• As a CF operator, I expect to know what horizontal and/or vertical scaling options are appropriate for individual Diego BOSH jobs so that I can provision my environment for redundancy efficiently (in flight)
• As a CF operator, I expect to have better guidance about how to adjust the resources that I provide to the BBS and Locket services so that I can maintain a stable CF control plane (in flight)

Cleanup

• cloudfoundry/rep #19: use the waitgroup instead, and return early to save some time.

BOSH job changes

None.

BOSH property changes

auctioneer

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

bbs

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

locket

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

rep and rep_windows

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

route_emitter and route_emitter_windows

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

ssh_proxy

• Added logging.format.timestamp: Controls the formatting style of the component log timestamp.

BOSH link changes

None.