cloudfoundry/diego-release v1.26.0

Diego v1.26.0

on GitHub

Changes from v1.25.3 to v1.26.0

• Verified with garden-runc-release v1.9.3.
• Verified with garden-windows-bosh-release v0.8.0.
• Verified with etcd-release v117.
• Verified with cf-mysql-release v35.
• Verified with cflinuxfs2-release v1.155.0.

NOTE: This version of Diego includes an experimental option to manage the Diego components as containerized processes with BPM. Opting into this mode for Diego components requires colocation of the bpm job from the BPM release with each component. After BPM publishes its first final release, we will publish an experimental operations file to enable this mode in the cf-deployment repository.

NOTE: This version of Diego includes an experimental option to disable the Diego components from registering themselves as Consul services. Opting into this mode requires usage of another service discovery mechanism for component connectivity, such as BOSH DNS with an appropriate set of aliases. The Release Integration team has upcoming work to publish a suitable BOSH DNS configuration to support a CF deployment.

Significant changes

BBS Relational Datastore

• As a Diego operator, I expect the max-pids migration to be idempotent so that it can be run again successfully even if the BBS schema version is not updated

De-Consuling Locks

• As a Diego operator, I expect each Diego Locket client to emit a metric about whether it holds a Locket lock

De-Consuling Service Discovery (Experimental)

• As a Diego operator, I expect to be able to disable Diego components from registering themselves as services with consul

Volume Support

• volman supports unmounting volumes through csi node plugins
• Add support for the volman to purge all the volumes.

v2 Loggregator API Adoption (Experimental)

• Remove compatibility package from go-loggregator
• cloudfoundry-incubator/go-loggregator #17: Remove source_instance tag
• cloudfoundry-incubator/go-loggregator #18: IngressClient.EmitLog batching messages by default can be confusing
• cloudfoundry-incubator/go-loggregator #19: Stop duplicating conversion logic
• go-loggregator requires v1 deps even if user is using v2
• Diego's v1 ValueMetrics are not being tagged with the meta data
• cloudfoundry/diego-release #356: Bump go-loggregator
• cloudfoundry/diego-release #357: Bump go loggregator to v4.0.1

Per-Instance Proxy (Experimental)

• Diego tasks should terminate correctly when the Envoy proxy is enabled in containers

BPM Integration (Experimental)

• Pair with Diego to add BPM support behind a feature flag
• As a Diego operator, I would like to be able to opt into using BPM to contain the Diego BOSH jobs so that I can take advantage of its simpler job lifecycle management and improved security

Multi-Buildpack Support

• As a buildpack-app-lifecycle consumer, I observe buildpack metadata for all buildpacks

App Logging and Metrics

• cloudfoundry/buildpackapplifecycle #23: BAL launcher will emit a harmless error when a binary app is pushed to CF

Component Logging and Metrics

• As a Diego operator, I would like better logging around executor client runners so that I can troubleshoot shutdown failures

Dependencies

• cloudfoundry/cfhttp #4: Consider setting net.Dialer.KeepAlive or http.Transport.IdleConnTimeout greater than zero

Documentation

• remove MetricsReportingDuration from bbs metrics in metrics docs
• Fix typo in d-r CONTRIBUTING.md doc

BOSH job changes

None.

BOSH property changes

auctioneer

• Added bpm.enabled: Whether to use BPM to manage the auctioneer process. Experimental.
• Added enable_consul_service_registration: Whether the auctioneer should register itself as a Consul service. Experimental to disable.

bbs

• Added bpm.enabled: Whether to use BPM to manage the BBS process. Experimental.
• Added enable_consul_service_registration: Whether the BBS should register itself as a Consul service. Experimental to disable.

file_server

• Added bpm.enabled: Whether to use BPM to manage the file-server process. Experimental.
• Added enable_consul_service_registration: Whether the file-server should register itself as a Consul service. Experimental to disable.

locket

• Added bpm.enabled: Whether to use BPM to manage the Locket process. Experimental.
• Added enable_consul_service_registration: Whether Locket should register itself as a Consul service. Experimental to disable.

rep

• Added bpm.enabled: Whether to use BPM to manage the cell rep process. Experimental.
• Added enable_consul_service_registration: Whether the cell rep should register itself as a Consul service. Experimental to disable.

rep_windows

• Added enable_consul_service_registration: Whether the cell rep should register itself as a Consul service. Experimental to disable.

route_emitter

• Added bpm.enabled: Whether to use BPM to manage the route-emitter process. Experimental.

ssh_proxy

• Added bpm.enabled: Whether to use BPM to manage the ssh-proxy process. Experimental.
• Added enable_consul_service_registration: Whether the ssh-proxy should register itself as a Consul service. Experimental to disable.

BOSH link changes

None.