Diego v2.36.0

Resources

• Download release v2.36.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 244c6ef40dbab44d2e98ad17dd5256a311e224a9.

Changes from v2.35.0 to v2.36.0

Significant changes

cfdot

• As a CF operator, I expect to understand that the ALG-based commands and events will be removed from cfdot no earlier than Diego v3.0.0

Routing

• repeating route deregistration messages causing errors for cf push/delete/push routine

Garden OCI Image Support (Experimental)

• As a CF Operator, I expect to be able to enable OCI mode on cells in my foundation and see that app instance disk usage includes the app droplet, so I can be confident my platform resources are being correctly accounted for

Per-Instance Proxy

• Envoy proxy binary bumped to 7b0ce0d32a9b584626e8c16b5ae07817eade322d

Buildpack Support

• Lifecycle can accept process types in launch.yml and bin/supply
• cloudfoundry/buildpackapplifecycle #38: Large credhub interpolation value causes app to not stage or start

Windows Support

• Refactor inigo and develop setup scripts to get instance identity tests working on Windows

Component Logging and Metrics

• As a CF Operator, I want to see a metric on how many app instances are exceeding the 10 second graceful shutdown interval when they are being stopped so that I can understand how the current 10 second global value is impacting app consumer experience
• As a Diego operator, I expect to be able to consume key performance indicator metric visualizations for the auctioneer 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 route-emitter so I do not have to build my own dashboards and can leverage the Diego team's operational expertise

Dependencies

• Bump routing-release dependencies in diego-release to stay up to date

Test Suites and Tooling

• Fix electron-cannon vizzini panic failure
• investigate why warp drive windows canary app experienced downtime during deploy
• investigate vizzini StartTimeout test failures

Cleanup

• As a CF operator, I expect the ssh-proxy and any other Diego components to use the new "flattened" ActualLRP API endpoints and associated instance-specific event types instead of ActualLRPGroup-based ones so that they will continue to function after their future removal

Sidecar Support

• As a BBS client, I expect to be able to create and fetch DesiredLRPs with a "sidecar" definition
• As a Diego operator, I expect when I desire an LRP with a sidecar definition, the sidecar action is run in my LRP container

BOSH job changes

BOSH property changes

None.

BOSH link changes

None.