The New Stack Podcast

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

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

Abby Kearns talks about the Cloud Foundry Summit, the focus on diversity and inclusion and how the organization will extend its open source footprint.

Watch on YouTube: https://youtu.be/noPHBCPvRzs

Abby Kearns talks about the Cloud Foundry Summit, the focus on diversity and inclusion and how the organization will extend its open source footprint.

Watch on YouTube: https://youtu.be/noPHBCPvRzs

Abby Kearns talks about the Cloud Foundry Summit, the focus on diversity and inclusion and how the organization will extend its open source footprint.

Watch on YouTube: https://youtu.be/noPHBCPvRzs

John Gossman is the lead architect on the Azure team at Microsoft. He has been at Microsoft for 17 years, seeing how the company has transitioned to being more open source oriented than ever before. But Microsoft has always been a company with a focus on developers. Now, the developer communities are open source, making for changes internal to the company on how it adapts to this new world of open application development.

Watch on YouTube: https://youtu.be/xW1GmYm9ieM

John Gossman is the lead architect on the Azure team at Microsoft. He has been at Microsoft for 17 years, seeing how the company has transitioned to being more open source oriented than ever before. But Microsoft has always been a company with a focus on developers. Now, the developer communities are open source, making for changes internal to the company on how it adapts to this new world of open application development.

Watch on YouTube: https://youtu.be/xW1GmYm9ieM

John Gossman is the lead architect on the Azure team at Microsoft. He has been at Microsoft for 17 years, seeing how the company has transitioned to being more open source oriented than ever before. But Microsoft has always been a company with a focus on developers. Now, the developer communities are open source, making for changes internal to the company on how it adapts to this new world of open application development.

Watch on YouTube: https://youtu.be/xW1GmYm9ieM

There is no single way to monitor containers running in production. CA Technologies, which has been in the application monitoring field for the entirety of this decade, has its own strategy: to filter out the infrastructure-centric elements from container monitoring, and present to developers metrics that are tailored for the way they understand the system. Listen now to Kumar’s explanation of how such a system works in CA Technologies’ Tailored Views of Performance, the latest installment of The New Stack Makers podcast with Scott Fulton.