Version 0.1412.0 of Diego is recommended for use with CF v215.
Changes from 0.1398.0 to 0.1412.0
Known issues
- garden-linux-release v0.292.0 has a goroutine/memory leak associated to container creation. This leak was fixed in Garden story #100896804, which is included in v0.293.0 and later, and will be used by the Diego version to be recommended for use with CF v216. We recommend that operators of any long-term deployments of this version of Diego monitor the goroutine counts of the garden-linux processes and restart them safely if needed.
Breaking changes
- The BBS API server provides handlers for starting LRP auctions and stopping LRP instances: This changes the internal API endpoints on the auctioneer that handle requests for Task and LRP auctions. As long as the active auctioneer and converger processes are from the same release during a rolling update of a Diego cluster, units of work will eventually get assigned to cells. This configuration should happen naturally during a rolling update of a 2-AZ deployment with 1 brain VM per zone.
Other significant changes
- For instances based on preloaded rootfses, Diego should apply disk limits to and report disk usage from only that container's read/write layer
- As a CF developer, I expect my app to have CC's global staging environment variables in its environment when staging on Diego
- As a CF developer, I expect my app to have CC's global running environment variables in its environment when running on Diego
- As a Diego operator, when I run the DATs in no-internet mode, I expect to run the language-specific buildpack tests
- Document setup required to run SSH DATs in DATs README
- Diego core components take an instance ActualLRP through its lifecycle through the BBS API server
- Diego core components read tasks through the BBS API server
- Bump to cflinuxfs2 1.3.0
BOSH property changes
- Add
diego.bbs.auctioneer.api_url: Address for BBS server to connect to the auctioneer.