Skip to content

0.3.0
Compare
Choose a tag to compare
@dsabeti dsabeti released this 08 May 19:15
v0.3.0
171fede

Manifest Updates:

  • Routing API now gets deployed by default in cf-deployment. This should allow deployers to take advantage of other routing features (like routing isolation segments) without also needing to deploy the TCP router. This also removes the need for operations/use-postgres-tcp-routing.yml.
  • HTTP Route Emitters are deployed in local mode by default in cf-deployment. The experimental ops-files for enabling local HTTP Route Emitters are now no-ops, and will soon be removed.
  • Remove unnecessary scopes from UAA Clients
  • Garden is configured with cleanup_process_dirs_on-wait to true.

Ops-files:

  • locket.yml deploys Diego jobs with locket and uses it for distributed locking (instead of using consul).
  • scale-to-single-az.yml properly scales down the NATS static IPs.
  • use-latest-stemcell.yml allows deployers to use the latest stemcell version instead of the version encoded in the manifest.
  • bypass-cc-bridge.yml allows deployers to bypass the CC Bridge for most workflows. This will eventually be inlined to cf-deployment.yml.
  • The experimental enable-local-route-emitter-tcp.yml allows deployers to deploy with local TCP Route Emitters. This is still being verified, but will eventually be inlined to cf-deployment.yml.
  • The experimental enable-loggregator-v2-diego-cell.yml allows deployers to opt-in to the v2 API for the Metron Agent. This will eventually be inlined to cf-deployment.yml.
  • The experimental disable-etcd.yml allows deployers to deploy without an etcd cluster and use links for loggregator components instead. This will eventually be inlined to cf-deployment.yml.

Transition from cf-release: You might have noticed a transition directory in cf-deployment. This is where we're keeping our experimental tooling for migrating cf-release to cf-deployment.

  • Currently, the primary tool there is transition.sh, which builds a vars-store from an existing CF and Diego manifest. You must also provide a file with the private keys use by the internal CAs for your deployment.
  • We also have a ops-file, test/cfr-to-cfd-transition.yml, for testing the migration process. When we're ready for people to use this ops-file to migrate to cf-deployment, we'll move it out of the test directory.
Assets 2
Loading