[cf-dev] Removing Consul support from capi-release

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[cf-dev] Removing Consul support from capi-release

Tim Downey
Hello everyone!

As you're likely aware, in 2017 Cloud Foundry began moving away from using Consul for distributed locks and service discovery. Additionally, last year's release of cf-deployment 5.0.0 removed it as a default component of CF completely.

We have begun the process of removing Consul support from some of the jobs in capi-release, starting with the cc-uploader. This means that as of the next capi-release (1.83.0), staging will no longer work in deployments that are relying on Consul for discovery. If you're using cf-deployment (BOSH DNS) or some other mechanism for service discovery this should not cause any issues.

Tim Downey, Connor Braa, and the CAPI Team


You receive all messages sent to this group.

View/Reply Online (#8649) | [hidden email] | [hidden email] | Mute This Topic | New Topic

Your Subscription | [hidden email] | Unsubscribe [[hidden email]]