Kubernetes Trials & Tribulations: Cloud, Data Center, Edge

The race to the cloud over the past two decades has been fast and furious. The ease and flexibility of turning on services when you want them, turning them off when you don’t, is an enticing prospect for developers as well as application deployment teams, but it has not been without its challenges. Many cite expanding costs, data sovereignty, or security as reasons for repatriation of workloads, but what about other factors, such as data gravity, latency, and extending workloads to the edge? Kubernetes platforms offer a unique cloud-like experience — all the flexibility, elasticity, and ease of use — with the added benefit of a common user experience regardless of where it is deployed — on premises, in a private or public cloud, even at the edge. It also allows organizations to run different workloads on different underlying platforms by abstracting the system layer, creating a seamless hybrid and multicloud strategy. We even see more and more service providers offering Containers-as-a-Service regardless of where the physical infrastructure resides. Our panel of experts will debate these issues, discussing: • So how are all these trends coming together? • Is cloud repatriation really a thing? • How are traditional hardware vendors reinventing themselves to compete? • Where does the data live? • How is the data accessed? • What workloads are emerging?