cloudfoundry/diego-release v2.9.0

Diego v2.9.0

on GitHub

Changes from v2.8.0 to v2.9.0

• Verified with cloudfoundry/cf-deployment @ 402208fabd058d77dcc8a808fa17afb48be8b3fb.
• Verified with garden-runc-release v1.14.0.
• Verified with garden-windows-bosh-release v0.14.0.
• Verified with cflinuxfs2-release v1.216.0.

IMPORTANT: This version of Diego does not shut down application processes gracefully with a TERM signal, and instead typically sends them only a KILL signal shortly after stopping the workload container. The Diego team recommends that platform operators use Diego v2.10.0 or later instead of this release.

Significant changes

Container Execution

• As a BBS API client, I expect that a Diego cell that fails to create a Task container to submit the Task for re-placement
• As a CF app end user, I expect my requests not to be directed to an app instance that crashed during startup

Component Coordination

• cloudfoundry/bbs #31: Fixed issue #30.

De-Consuling Service Discovery (Experimental)

• As a CF operator, I expect to be able to create a CF deployment with several diego-api instances regularly when both BOSH DNS and a networking add-on such as IPsec is enabled so that I can deploy reliably

Rootless Garden Integration

• As a Diego contributor, I expect to be able to skip privileged-container tests when I run the vizzini test errand so that I can run vizzini against an environment that does not support privileged containers (in flight)

Component Logging and Metrics

• cloudfoundry/route-emitter #13: fix logger session traceability in routingtable

Dependencies

• Fix diego-release NATS dependency

Cleanup

• Ignored Errors in bbs/db/sqldb/task_convergence.go
• refactor AllocateContainers in executor.client to not return an error

BOSH job changes

None.

BOSH property changes

vizzini

Added enable_privileged_container_tests: Whether to run tests that make privileged containers. Defaults to true.

BOSH link changes

None.