cloudfoundry/diego-release v1.3.0

Diego v1.3.0

on GitHub

Changes from v1.2.0 to v1.3.0

• Verified with garden-runc-release v1.0.4.
• Verified with garden-windows-bosh-release v0.1.0.
• Verified with etcd-release v87.
• Verified with cf-mysql-release v32.
• Verified with cflinuxfs2-rootfs-release v1.43.0.

IMPORTANT: DO NOT USE this version of Diego if you set the diego.executor.disk_capacity_mb or diego.executor.memory_capacity_mb BOSH properties to explicit numeric values, instead of relying on the "auto" default. The configuration refactoring of the cell rep in story #135348391 accidentally introduced a regression that prevents the cell rep from starting with these numeric values configured. The Diego team will release Diego v1.3.1 with a fix as soon as possible.

Significant changes

Routing

• As a Diego operator, I expect the HTTP route-emitter to stop registering routes for evacuating instances as early as is safely possible

Local Route Emitters (Experimental)

• As a Diego operator, I expect to be able to run the route-emitter in an experimental cell-local mode

Dependencies

• Update to Golang v1.7.4+ in diego-release

Test Suites and Tooling

• As a Diego operator, I expect the examples/aws bosh-init instructions to include configuration for a health-monitor user so that the health monitor can send appropriately tagged metrics to datadog
• As a CF operator, I expect the AWS examples to include instructions for generating and using UAA and loggregator TLS credentials (in flight)
• Investigate a hanging cfdot integration test

Security

• The bbs can respond to staging callbacks directly to the cc with Mutual TLS

Cleanup

• Convert the rep to use a JSON configuration file rather than command line flags.

BOSH job changes

None.

BOSH property changes

• Added diego.rep.job_name: Used to distinguish between the rep and rep_windows jobs.
• Added diego.route_emitter.local_mode: Experimental flag to enable cell-local mode for the route-emitter job.