cloudfoundry/diego-release v2.31.0

Diego v2.31.0

on GitHub

Resources

• Download release v2.31.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 6c760d8720a18c30946df7f8cbef5c150455edfd.

Changes from v2.30.0 to v2.31.0

Significant changes

BBS API

• As a BBS API client, I expect the SHA-512 digest algorithm to be deprecated in the image-layer spec so that I avoid adopting it accidentally before its future removal
• As a BBS API client, I expect to understand that the ActualLRPGroup message and associated BBS API endpoints are deprecated and will be removed no earlier than Diego v4.0.0

BBS Benchmarks

• Fixed failing BBS Benchmark Build

Performance Tuning

• As a CF operator, I expect that locket should release idle database connections so that it does not take an outsize share of the shared CF database resources

Local Route Emitters

• As a CF operator, I expect the Diego route-emitter to use the new "flattened" ActualLRP API endpoints and associated instance-specific event types instead of ActualLRPGroup-based ones so that it will continue to function after their future removal
  • Investigate and resolve an increase in 502s that was introduced by the above change (prior to release) from canary app on warp-drive and electron-cannon

Container Networking Support

• As a Diego operator, I would like the executor's garden healthcheck containers to have shorter distinct container handles so that their egress-rule iptables chains are unlikely to collide (take 2)

Per-Instance Proxy

• As a CF operator, I expect not to see spurious error messages about proxy config directory deletions in the rep logs so that I am not distracted or concerned about behavior that is actually normal
• Bumps Envoy proxy binary to 78ad883b70764c27f8b391ee3a5056a64b403426

Component Logging and Metrics

• Investigate benchmark bbs failure
  • Add DBWaitCount and DBWaitDuration metrics for BBS and Locket
• As a Diego operator, I expect to observe a metric that indicates when a Diego cell has stopped accepting work specifically because Garden is not functioning correctly so that I can diagnose the Garden malfunction
  • UnhealthyCell metric deprecated in favor of GardenHealthCheckFailed.

Test Suites and Tooling

• Remove vizzini rootfs tests because it is redundant
• Change references to cflinuxfs2 in diego-release to cflinuxfs3
• validate that DUSTs can be run from a workstation locally
• rewrite vizzini download-cancellation test because it is not testing what it should be

Documentation

• clean up diego-release contributing docs, remove obsolete references (to cf-release, go versions, etc.)

BOSH job changes

• NONE

BOSH property changes

• NONE

BOSH link changes

• NONE