Re: Update: Locks & Service Discovery in CF Runtime
The road off Consul looks like it is long but necessary. Consul looks like a spof in CF, when you know how much the platform needs it, and when you read that sometimes plain upgrades break it badly.toggle quoted messageShow quoted text
Plus, the myriad of logic in the confab wrapper around Consul is an example of how much Consul is hard to manage and keep up properly.
Don't forget that recently PCF benefitted a CRE (SRE-tye) shared review from Google.
Don't forget that we have converging evidences that let us think Google stays away from etcd for their hosted K8s on GCP.
My guess is that internally, Google SREs might have evidences at scale that systems like etcd or consul should be avoided, and this understanding is being ported to CF through the CRE program.
Also, moving away from Consul is like choosing to build Diego instead of building on top of K8s. Controlling the agenda is important. I mean not being forced to run after a project that has its own. Ensuring which value is put into the product, and that this value is consistent with the rest of the platform, is also important.
These are just thoughts. I would love to read more precise info about the Why, for this "away-from-Consul" move. Guys?
Le 26 avr. 2017 à 18:48, Voelz, Marco <marco.voelz(a)sap.com> a écrit :