You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release of cf-deployment includes an update of garden-runc-release that uses GrootFS by default. As such, there will be changes to some ops-files (see below). An important note for operators: it is recommended to recreate cells shortly after upgrading; we've managed to include a stemcell update as part of this release, so that should happen automatically for anybody using the stemcell specified in cf-deployment.yml.
This release removes several deprecated loggregator metrics. See the Loggregator 101.4 release notes for details.
Ops-files
New ops-files
experimental/use-shed.yml allow operators to opt in to using the legacy "shed" FS from older versions of garden.
legacy/keep-original-routing-postgres-configuration.yml allows operators to override the database names and database usernames for the Routing API database on the postgres node. Because cf-deployment hard-codes the database names and usernames, anyone migrating their postgres node from cf-release whose deployment also included a Routing API will need this ops-file to maintain their previous configuration.
Updated ops-files
experimental/use-grootfs.yml is a no-op.
experimental/enable-oci-phase-1.yml no longer has a dependency on experimental/use-grootfs.yml
