Kubernetes’ native strategy for high availability is to set up multiple master replicas, and engineer a failover system that passes control to a replica when the main master fails. When the master does fail, nothing can schedule workloads. But the problem with simplicity — here and everywhere else — is that it makes things way too complex. There are a variety of approaches to resolving this issue, and providing what the architects of these approaches politely describe as real high availability (perhaps we should call it “RDA”). Some involve a kind of replication of the entire Kubernetes environment. Kubo is Cloud Foundry’s contribution to this emerging group of alternatives. It’s a way of leveraging the features that Cloud Foundry already uses for load balancing virtual machines, for effectively balancing traffic to multiple Kubernetes instances inside VMs. Watch on YouTube: https://youtu.be/12JfRZmKqx4
Kubernetes’ native strategy for high availability is to set up multiple master replicas, and engineer a failover system that passes control to a replica when the main master fails. When the master does fail, nothing can schedule workloads. But the problem with simplicity — here and everywhere else — is that it makes things way too complex.
There are a variety of approaches to resolving this issue, and providing what the architects of these approaches politely describe as real high availability (perhaps we should call it “RDA”). Some involve a kind of replication of the entire Kubernetes environment. Kubo is Cloud Foundry’s contribution to this emerging group of alternatives. It’s a way of leveraging the features that Cloud Foundry already uses for load balancing virtual machines, for effectively balancing traffic to multiple Kubernetes instances inside VMs.
Watch on YouTube: https://youtu.be/12JfRZmKqx4