Diego v2.20.0

Resources

• Download release v2.20.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 483d04f15c334652dd192882417b7bc8fdf982ce.

Changes from v2.19.0 to v2.20.0

Significant changes

BBS API

• cloudfoundry/bbs #34: image_layer.proto not valid when compiled to Ruby (for Cloud Controller)

Container Execution

• As a CF operator, I expect the cell rep to put a network-namespaced property on its garden-healthcheck containers so that the container networking Garden plugin can distinguish it from LRP or Task containers

Routing Stability: Suspect Cells and ActualLRPs

• As a CF operator, I expect to be able to use cfdot to list all of the ActualLRPs for a DesiredLRP when one of them is running on a suspect cell
• As a BBS API client, I expect to be able to see instance-specific events for ActualLRPs as they go through cell state changes so that I can understand changes to a single instance
• Investigate and fix event-handler nil-dereference panics

Volume Support

• nfsv3driver drain logic doesn't get stuck if there are bad or stuck mounts
• cloudfoundry/executor #38: Ensure volumes get unmounted even when garden fails to destroy the container
• cloudfoundry/lager #35: Add redactingPrettySink class for log filtering with formatted timestamps and log level

Garden OCI Image Support (Experimental)

• As a BBS API client, I expect the BBS to allow me to retrieve LRPs and Tasks with declarative resources so that I can inspect the assets that have been specified
• bbs panics in event handler when desired lrp changed events occur

Per-Instance Proxy (Experimental)

• As a CF contributor, I expect the Envoy binary in diego-release to include the fix to issue #4409 (from PR #4684) so that I can start reconfiguring it to use the secret discovery service APIs

Rootless Garden Integration

• cloudfoundry/diego-release #414: Make possible for garden to access shared data in rootless

App Logging and Metrics

• cloudfoundry/diego-logging-client #6: Introduce SendCPUUsage client method
• cloudfoundry/executor #35: Send CPU usage to metron client

Component Logging and Metrics

• As a Diego operator, I expect to see metrics about the BBS's usage of its backing database so I can better diagnose errors related to database contention

Security

• As a CF operator, I expect to be able to connect the BBS and Locket to a database with only CA verification of the host so that they can connect over TLS to Google Cloud SQL and Azure SQL databases

Documentation

• Complete BBS API deprecation docs after #158949366

BOSH job changes

None.

BOSH property changes

bbs

• Added database.tls.enable_identity_verification: Whether to verify the identity of the backing database when connecting over TLS. Defaults to true.

locket

• Added database.tls.enable_identity_verification: Whether to verify the identity of the backing database when connecting over TLS. Defaults to true.

BOSH link changes

None.