cloudfoundry/diego-release v2.6.0

Diego v2.6.0

on GitHub

Changes from v2.5.0 to v2.6.0

• Verified with cloudfoundry/cf-deployment @ d62bf37da92c085a23c002de172369790e6a0ab8.
• Verified with garden-runc-release v1.13.1.
• Verified with garden-windows-bosh-release v0.14.0.
• Verified with cflinuxfs2-release v1.203.0.

Significant changes

Container Placement

• As a BBS API client, I expect to see task_changed events in the Task-event stream when Tasks fail placement

Instance Identity Credentials

• As a CF operator, I expect to find information about instance-identity credential configuration in the CF docs website so that I can enable it correctly
• As a CF app developer, I expect to have documentation about the properties of instance-identity credentials so that I can use them appropriately for app communication
• As a CF app developer, I expect the instance-identity credentials certificate also to include the org and space guids so that I can use them to satisfy broader CF authorization predicates (in flight)

Declarative Health Checks

• As a CF operator, I expect my Diego cells to opt into preferring declarative healthchecks by default so that I can automatically benefit from this stability improvement

Per-Instance Proxy (Experimental)

• As a CF operator, I expect to understand how the Envoy proxies consume memory resources under concurrent request load so that I can provision resources appropriately to support route-integrity improvements
• As a CF app developer, I expect my app instances to be able to handle more than 1024 concurrent connections even if the Envoy proxy is enabled on its host cells

Component Logging and Metrics

• As a CF operator, I expect the RFC3339-formatted lager timestamps always to have exactly 9 decimal places so that I can use sort to sort them chronologically

Dependencies

• As a Diego operator, I expect the release to use Golang v1.10.2+ so that I am up to date with this important dependency

Security

• As a CF operator, I expect the cell rep job not to affect the kernel configuration when running in a container itself so that it does not affect other jobs or processes on the host

Cleanup

• Remove event filtering logic from route-emitters

BOSH job changes

None.

BOSH property changes

rep and rep_windows

• Changed containers.proxy.additional_memory_allocation_mb default value from 5 to 32.
• Removed experimental status of enable_declarative_healthcheck.
• Removed experimental status of declarative_healthcheck_path.

BOSH link changes

None.