cloudfoundry/diego-release v2.32.0

Diego v2.32.0

on GitHub

Resources

• Download release v2.32.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ b8e2976f7340db0bfa5180cc1382c9e968f7d431.

Changes from v2.31.0 to v2.32.0

Significant changes

BBS API

• cloudfoundry/diego-release #428: BBS Crashing and Failing over
  • updated how bbs handles context cancellations to eliminate concurrent map read/writes panic's which could cause the BBS to crash/failover.

LRP Convergence

• As a Diego operator, I expect the BBS to be able to run convergence successfully on desired LRPs that have > 283 instances when my backing store is MySQL so that I do not have extra error messages in my BBS logs and do not have undesired ActualLRPs running

SSH

• cloudfoundry/route-emitter #14: Enable cf ssh for Windows+Linux with 3rd Party Network Plugins + bbs #166247777 + diego-ssh #166247920 + executor #166247994 + rep #166248025
  • A new property on the Rep job, advertise_preference_for_instance_address allows the ability to cf ssh to apps on heterogenous foundations (Linux and Windows Diego cells) when third-party container network interface (CNI) plugins are present. Previously on such environments, cf ssh would work to only Windows OR Linux apps, but not both.
  • During your upgrade deployment to a heterogeneous foundation which includes a third-party container network interface (CNI) plugin:
    • cf ssh to Linux apps should continue to work although there may be short outage as the instance groups containing the ssh_proxy and rep jobs begin to roll
    • cf ssh to Windows apps should start working once the windows diego-cells begin to roll
    • There should be no app availability downtime for either Windows or Linux apps during the upgrade
  • During your upgrade deployment to a foundation which doesn't include a third party container network interface (CNI) plugin:
    • cf ssh to both Linux AND Windows apps should continue to work although there may be short outage as the instance groups containing the ssh_proxy and rep jobs begin to roll
    • There should be no app availability downtime for either Windows or Linux apps during the upgrade

Routing

• Bump routing-api in diego-release (currently ref's a SHA from 2017)

Per-Instance Proxy

• Envoy proxy binary bumped to 619dcbe469d17114ab5c9b079f46866f0f5ce296

Windows Support

• As a CF operator, I expect that Windows Diego cell reps deployed to Azure configure their zone based on the assigned Azure Fault Domain or Azure Availability zone when I opt-in to doing so, so that the auctioneer can make appropriate LRP instance placements

App Logging and Metrics

• As a Diego operator, I expect to be able to consume key performance indicator metric visualizations for Locket so I do not have to build my own dashboards and can leverage the Diego team's operational expertise

Component Logging and Metrics

• Investigate high log volume being sent to logit.io
  • In an effort to minimize the number of logs under Info, we removed and re-arranged a few places where we believe it's unneccessary executor / 0dc5df0

Test Suites and Tooling

• cloudfoundry/diego-release #430: Introduce a ifrit startcheck timeout configuration

BOSH property changes

rep and rep_windows

• Added advertise_preference_for_instance_address in developing against the "Enable cf ssh for Windows+Linux with 3rd Party Network Plugins" feature stories described in the SSH section of these release notes (default value: false)