Diego v2.4.0

Changes from v2.3.0 to v2.4.0

• Verified with cloudfoundry/cf-deployment @ fca6dced5e7c094de57ae48c26505ca72d0bb22b.
• Verified with garden-runc-release v1.12.1.
• Verified with garden-windows-bosh-release v0.13.0.
• Verified with cflinuxfs2-release v1.196.0.

Significant changes

Per-Instance Proxy (Experimental)

• As a BBS API client, I expect the cells to run LRP instances without memory limits as specified even if the cells supply Envoy proxies with an additional memory allocation
• As a CF app developer, when my app instance crashes because the sidecar Envoy proxy process exits, I expect to see information about that reason in the app instance logs and crash reason so that I can distinguish it as a platform issue and not an issue with my application

Windows Support

• cloudfoundry/diego-release #388: Add getenv binary to BAL and WAL.
• apps with newlines in environment variables should be pushable to windows cells

App Logging and Metrics

• As a CF app operator, I expect the disk usage for my Docker-image-based app instances to include the size of the image layers so that I can correctly understand the amount of disk space remaining in each instance

Component Logging and Metrics

• cacheddownloader should not mask the original error encountered in the download if the step is cancelled
• As a CF operator, I expect to be able to determine which goroutines in my Diego components prevented a shutdown within the time monit allows so that I can provide useful details to resolve this behavior in the future

Documentation

• As a CF operator, I expect to know what horizontal and/or vertical scaling options are appropriate for individual Diego BOSH jobs so that I can provision my environment for redundancy efficiently
• As a CF operator, I expect to have better guidance about how to adjust the resources that I provide to the BBS and Locket services so that I can maintain a stable CF control plane

BOSH job changes

None.

BOSH property changes

None.

BOSH link changes

None.