Please note: All times listed below are in Central Time Zone
Enterprises are increasingly wanting to consume OpenStack as a Managed Service to avoid the complexity of running it themselves. As they adopt kubernetes, many view kubernetes on bare metal as an alternative to OpenStack for microservice workloads. We will explore kubernetes on bare metal and kubernetes on OpenStack for private clouds, what drives enterprise preference and perception, and the journey for these customers as their workloads and needs change over time.
Gain insight from industry luminaries on the questions for this panel. Understand where the experts agree, and perhaps where they don't.
Sample Questions for the Panel
- In a private data center context, initially enterprises are wanting to try kubernetes on bare metal without OpenStack. True or False?
- What interest do your see in Kubernetes, and what is driving customer behavior?
- The Kubernetes community plug-in ecosystem is enabling multiple options for networking, storage and compute. When is an IaaS layer like OpenStack something that should be introduced into a kubernetes microservice solution?
- What workloads or factors come in to play when thinking about whether to run Kubernetes with or without an IaaS layer like OpenStack?
- IaaS’ are all starting to look similar (AWS, OpenStack, GKE)… Does this mean Kubernetes on bare metal is just for market entry/experimentation, or do you see it as a viable alternative to Private Cloud on IaaS (OpenStack, VMWare, etc.)?
- From a Managed Services perspective, what does it look like to have separate solutions for Kubernetes on bare metal vs. Kubernetes on OpenStack?
- Or are Managed Service providers focusing on including an underlying IaaS platform? If so, why?