cloudfoundry/diego-release v1.30.1

Diego v1.30.1

on GitHub

Changes from v1.30.0 to v1.30.1

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

NOTE: This release fixes the defect with stopping long-running app instances that was introduced in Diego v1.30.0.

Significant changes

Container Execution

• As a Diego operator, I expect to be able to stop container instances when instance-identity credentials are enabled but the container proxy is not so that I do not run out of allocatable memory

cfdot

• As a Diego operator, I expect to be able to use cfdot to retrieve the states of all registered cells

SSH

• cloudfoundry/diego-ssh #38: identify diego-ssh server to clients

Routing

• Investigate canary blip on warp-drive, 2017-11-21, 5:42 PM PST
• cloudfoundry/route-emitter #10: Remove duplicate code and ensure all port mappings are unregistered when an actual lrp is removed

Per-Instance Proxy (Experimental)

• As a Diego operator, I expect to find container-proxy BOSH properties under containers.proxy so that I can comprehend the hierarchy of cell rep properties
• As a CF operator, I expect containers with a preloaded+layer rootfs are also opted into Envoy proxies and corresponding memory-quota adjustments so that I do not lose routing integrity
• As a CF code auditor, I expect the envoy blob name to include the commit SHA of the source code so that I can scan the corresponding source code for license and copyright information

Component Logging and Metrics

• As a Diego operator, I expect to see metrics about locket's usage of its backing database so I can better diagnose errors related to database contention
• As a Diego operator, when a cell strands ActualLRP instances during evacuation, I would like to be able to identify which ones and why so that I can understand why they failed to be placed
• As a Diego operator, I expect the rep's drain script to log to /var/vcap/sys/log/rep/drain.log so that I have a consistent dedicated place to look for that drain output

Dependencies

• cloudfoundry/clock #3: Don't refire with the same time after creating a ticker

BOSH job changes

None.

BOSH property changes

rep and rep_windows

• Added containers.proxy.enabled to replace container_proxy.enabled.
• Added containers.proxy.additional_memory_allocation_mb to replace container_proxy.additional_memory_allocation_mb.
• Removed container_proxy.enabled.
• Removed container_proxy.additional_memory_allocation_mb.

BOSH link changes

None.