cloudfoundry/diego-release v1.23.0

Diego v1.23.0

on GitHub

Changes from v1.22.0 to v1.23.0

• Verified with garden-runc-release v1.9.0.
• Verified with garden-windows-bosh-release v0.5.0.
• Verified with etcd-release v117.
• Verified with cf-mysql-release v35.
• Verified with cflinuxfs2-release v1.137.0.

Significant changes

Container Execution

• As a CF app developer, I expect app execution and logs not to be affected by newosproc error output and failures

cfdot

• As a cfdot user, I expect to be able to subscribe to a stream of Task events

De-Consuling Locks (Experimental)

• As a Diego operator, I expect that the locket server is resilient to a rolling deploy of its MariaDB cluster
• As a Diego operator, I expect each BBS and auctioneer instance to be able to reclaim its locket lock if it unexpectedly crashes without releasing the lock

v2 Loggregator API Adoption (Experimental)

• As a Diego operator, I expect the BBS to emit its component and Golang metrics via the v2 loggregator API if so configured

App Logging and Metrics

• As a CF app developer, I expect that the Diego system should report out-of-memory events in crash reasons and log lines only once

Documentation

• cloudfoundry/lager #27: update import locations in README
• As a Diego operator, I expect to be able to back my AWS Diego deployment with a cf-mysql-deployment-based MySQL cluster so that I can deploy the latest cf-mysql-release version (in flight)

BOSH job changes

None.

BOSH property changes

bbs

• Added loggregator.use_v2_api: Whether to use the v2 Loggregator API when sending component metrics to the local metron agent.
• Added loggregator.v2_api_port: Port for the v2 Loggregator API.
• Added loggregator.ca_cert: CA certificate to use to validate the v2 Loggregator API connection to metron.
• Added loggregator.cert: Certificate to present when connecting to the v2 Loggregator API.
• Added loggregator.key: Private key for the v2 Loggregator API client.

BOSH link changes

None.