cloudfoundry/diego-release v1.29.0

Diego v1.29.0

on GitHub

Changes from v1.28.0 to v1.29.0

• Verified with garden-runc-release v1.9.5.
• Verified with garden-windows-bosh-release v0.10.0.
• Verified with etcd-release v117.
• Verified with cf-mysql-release v35.
• Verified with cflinuxfs2-release v1.161.0.

Significant changes

BBS API

• When an app crashes, the BBS should emit a crash event, even if the BBS auction request fails

Container Placement

• As a Diego operator, I expect the set of rootfs providers in the cell registration payload to match those in rep state response so that I have a consistent understanding of the cell capabilities
• As a Diego operator, I expect to see more complete cell and instance identifiers in the state response so that I can understand the live state of the cell and its workload
• As a Diego operator, I expect the auctioneer to include the intended cell ID in its work assignments to cells and for the cell to refuse work that does not match its ID so that each cell runs the units of work the auctioneer intended to assign

Container Execution

• As a Diego operator, I expect the cell rep always to use its first preloaded rootfs as the base image for the garden healthcheck

Instance Identity Credentials (Experimental)

• rep/executor should include the external IP as an IP SAN in the instance-identity certificate if the internal IP is not set on the container

v2 Loggregator API Adoption (Experimental)

• Eliminate runtimeschema/metric package, and convert remaining references to it to use new loggregator api
• Update go-loggregator and diego to not use gauge metrics for instance id in container metrics
• cloudfoundry/diego-logging-client #2: Updates SendAppMetrics to use new go-loggregator GaugeAppInfo
• cloudfoundry/diego-release #361: Set InstanceIndex as meta information in envelope instead of value
• enforce a canonical import path for the diego-logging-client library

Secure Service Instance Credentials (Experimental)

• As a buildpack app developer, my unmodified app bits will launch on a credhub-enabled foundation
• As a lone user of the launcher, I observe that DATABASE_URL is set automatically
• As a CF app developer, I expect my Docker app instances to start when either CredHub or instance-identity credentials are unavailable if my service bindings contain no CredHub references
• As a buildpack app developer, my unmodified app bits will stage on a credhub-enabled foundation
• cloudfoundry/diego-release #368: bump buildpackapplifecycle

Buildpack Support

• As a buildpack developer, I am able to place .profile.d scripts outside of the app directory on newer foundations

Docker Support

• cloudfoundry/diego-release #353: dockerapplifecycle doesn't work with Azure private registries - update dependency

Component Logging and Metrics

• As a Diego operator, I expect each Diego cell to emit metrics about the disk and memory capacity allocated and used by containers so that I can estimate capacity advertisements safely
• Add additional logging around SQL runner

Test Suites and Tooling

• Run LOCAL vizzini tests in CI
• fix the flaky ssh tests on warp-drive and electron-cannon

Documentation

• As a Diego operator, I expect to have clear documentation about BBS encryption key rotation so that I can safely remove a compromised key

BOSH job changes

None.

BOSH property changes

None.

BOSH link changes

None.