cloudfoundry/diego-release v1.33.0

Diego v1.33.0

on GitHub

Changes from v1.32.2 to v1.33.0

• Verified with garden-runc-release v1.11.0.
• Verified with garden-windows-bosh-release v0.13.0.
• Verified with etcd-release v117.
• Verified with cf-mysql-release v35.
• Verified with cflinuxfs2-release v1.181.0.

IMPORTANT – ACTION MAY BE REQUIRED: If you still use the "legacy" Diego deployment manifests that the generate-deployment-manifest script produces instead of cf-deployment, then you MUST upgrade to garden-runc v1.11.0 to be compatible with the manifest changes. This coordinated change is required because this version of the garden-runc release makes grootfs its default image-layer management system. Please see the cf-dev announcement for more details.

Significant changes

Container Execution

• cloudfoundry/diego-release #377: Apps health check failed with malformed HTTP response message - SSH-2.0-diego-sshd

Manifest Generation

• As a CF operator, I expect to be able to use "classic" diego-release manifest generation with garden-runc-release v1.11.0 and later
• As a Diego operator, I expect the cfdot jobs in cf-deployment no longer to use the deprecated diego.cfdot.bbs properties

Component Logging and Metrics

• As a Diego operator, I expect the BBS not to report error-level logs for API resources that are not found so that I do not misconstrue the errors as anomalous behavior

Test Suites and Tooling

• Diego team should own and maintain assets used in vizzini
• As a Diego contributor, I expect to be able to run the latest vizzini test suite against a locally deployed Diego with different combinations of v1.0.0 and latest components
• As a Diego contributor, I expect to be able to verify continuity of application uptime and routability during an upgrade from Diego v1.0.0 to the latest version
• BBS benchmark dashboards should report BBS LRP convergence duration metrics during benchmark runs

BOSH job changes

None.

BOSH property changes

None.

BOSH link changes

None.