3 ms·
Etcd misbehaving during upgrades or when a VM was replaced was a massive source of bugs for Cloud Foundry. There is no longer an etcd anywhere in Cloud Foundry
by jacques_chester 8y ago
Etcd misbehaving during upgrades or when a VM was replaced was a massive source of bugs for Cloud Foundry.
There is no longer an etcd anywhere in Cloud Foundry.
- ec109685 8y agoAren’t they introducing Kubernetes as part of Cloud Foundry: https://techcrunch.com/2018/04/20/kubernetes-and-cloud-foundry-grow-closer/ https://techcrunch.com/2018/04/20/kubernetes-and-cloud-found...
- jacques_chester 8y agoSort of. Kinda. It's complicated. But insofar as Kubernetes becomes the container orchestrator, I imagine we will encounter some or all of those problems again. Cloud Foundry's current orchestrator, Diego, is of similar vintage to Kubernetes. It now relies entirely on relational databases for tracking cluster state. Ditto other subsystems (eg, Loggregator). It scales just fine. MySQL, while not my personal favourite, has proved more reliable in practice than etcd. Some folks use PostgreSQL. Also more reliable in practice. Paying customers care more about being more reliable in practice than being more reliable in theory. I've ha-ha-only-seriously suggested we throw engineering support behind non-etcd cluster state. For example: https://github.com/rancher/k8s-sql https://github.com/rancher/k8s-sql