Changes from v2.4.0 to v2.5.0
- Verified with cloudfoundry/cf-deployment @
b70090f9237b5e24ab86410842b0288bcf6862f1
. - Verified with garden-runc-release v1.13.1.
- Verified with garden-windows-bosh-release v0.13.0.
- Verified with cflinuxfs2-release v1.203.0.
Significant changes
BBS API
Container Placement
- As a CF operator, I expect to be able experimentally to opt Diego into retrying placement of a Task a limited number of times so that Task placement can be more resilient to transient drops in addressable capacity
- As a BBS API client, I expect to see placement errors and placement failure counts on Tasks so that I can understand why they are still Pending
SSH
- As a CF app developer, I expect to be able to create remote SSH tunnels to my app instances so that I can connect them to network resources local to my workstation
- As a CF operator, I expect the ssh_proxy's diego.ssh_proxy.uaa.port property to default to 8443 so that I do not have to supply it in my CF manifest
- As a CF Java developer, I expect the default CF SSH cipher suites, MACs, and key exchange algorithms to be compatible with the SSHJ client library so that I can use existing Java developer tooling against my CF deployment
Per-Instance Proxy (Experimental)
- As a CF operator, I expect to understand how the Envoy proxies consume memory resources under concurrent request load so that I can provision resources appropriately to support route-integrity improvements (in flight)
- As a CF operator, I expect to be able to run at least 250 container instances on my proxy-enabled Linux Diego cells so that my container density is not artificially limited
App Logging and Metrics
BOSH job changes
None.
BOSH property changes
bbs
- Added
tasks.max_retries
. Experimental: number of times to retry placement of a Task. Defaults to0
.
ssh_proxy
- Updated
diego.ssh_proxy.uaa.port
to have a default value of8443
.
vizzini
- Added
max_task_retries
: Whether to run acceptance tests for task placement retries.
BOSH link changes
None.