Diego v2.37.0

Resources

• Download release v2.37.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 5d9063c5b93b6e928fab7e58c0efecc9b369bf81.

Changes from v2.36.0 to v2.37.0

Significant changes

Component Coordination

• As a CF operator, I expect my diego-cell deployment to succeed consistently through various startup orders of the services on my cell (bosh-dns/route-emitter) and invalid secondary DNS servers

Cell Capacity Reporting & LRP Placement

• As a CF operator, I do not want the advertised disk capacity of my foundation's cells to be greater than what is actually usable by garden on those cells so I can be sure apps pushed to the foundation do not fail due to the cell running out of actual disk space

Local Route Emitters

• As a Diego operator, I expect that the communication between the route emitter and routing API to be over mTLS so I can be sure of the security of my foundation

Volume Support

• remove CSI support from Diego
• cloudfoundry/diego-upgrade-stability-tests #1: remove CSI support from Diego
• cloudfoundry/executor #47: remove CSI support from Diego
• cloudfoundry/inigo #21: remove CSI support from Diego
• cloudfoundry/rep #29: remove CSI support from Diego
• cloudfoundry/diego-release #437: remove CSI support from Diego
• update troubleshooting guide for volume services

Per-Instance Proxy

• Envoy proxy binary bumped to 882a30677619856446f7e1b9d28c6ab319b21d1b

App Logging and Metrics

• cloudfoundry/executor #30: fix unexpected container CPU usage figure

Component Logging and Metrics

• As a CF operator, I expect not to see the auctioneer handle an empty placement request when a BBS API client creates a 0-instance DesiredLRP so that I am not confused by extraneous Diego component activity
• As a Diego operator, I expect to be able to consume key performance indicator metric visualizations for the BBS so I do not have to build my own dashboards and can leverage the Diego team's operational expertise
• As a Diego operator, I expect to be able to consume key performance indicator metric visualizations for the rep so I do not have to build my own dashboards and can leverage the Diego team's operational expertise
• As a Diego operator, I expect the indicator document for the auctioneer to include a metric that indicates if the auctioneer lock is held so I can be sure my foundation is healthy
• Audit runtime metrics being emitted by our components and clean up Diego release docs for those that no longer exist

Dependencies

• As a CF operator, I expect Diego components to use Golang 1.12.9 so that they are up to date with this important dependency
• Bump grpc go to v1.23.0

Test Suites and Tooling

• Remove error ignoring in vizzini that was bypassing GCP load balancer error
• cloudfoundry/inigo #21: remove CSI support from Diego

Security

• As a Diego operator, I expect that the communication between the route emitter and routing API to be over mTLS so I can be sure of the security of my foundation

BOSH property changes

rep and rep_windows

• The following properties have been deleted from both rep and rep_windows to remove CSI support from Diego
  • diego.executor.volman.csi_paths
  • diego.executor.volman.csi_mount_root_dir
• The following property has been added to both rep and rep_windows
  • diego.executor.use_schedulable_disk_size