Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week’s episode, we spoke with Tina Nolte, vice president of product, for Kubernetes management service Spectro Cloud, about why we shouldn’t think of containers/Kubernetes as just another form of virtualization.
Nolte recently wrote a popular post for us on why we shouldn’t think of containers and Kubernetes as just another form of virtualization — that it opens up a whole new way to think about application development and deployment. So we wanted to find out more about this concept.
“Kubernetes is really about that middle area between infrastructure and application. So the applications themselves are enabled to be differently architected because that operational PaaS layer, if you will,” she explained. “It’s not just a lift-and-shift of old apps into new infrastructure.”
Focusing too much on the infrastructure side of Kubernetes ultimately misses its true value, an insight Nolte gleaned, in part, from working for a well-regarded OpenStack-based start-up, Nebula, that ultimately shuttered. From our conversation:
Most enterprise OpenStack vendors focused on sort of a public cloud competition path, if you will. However, I think because of that deeply rooted in infrastructure focus, most of those vendors didn’t acknowledge the value of the platform services that the public cloud offered,” She said. “There’s something I heard once, where everybody thinks that their layer in the stack is where the hard problems are. That every layer above them is easy. If you’re deeply entrenched in infrastructure thinking, you don’t appreciate the ways in which that ecosystem is developing above you.
We also delved into the Kubernetes services that Spectro Cloud offers. We keep hearing again and again about the operational complexities of managing Kubernetes. So we learn how the company eases this process.
“So our aim is to remove the trade off between control and ease-of-use when an enterprise is considering their Kubernetes infrastructure stack. And that’s regardless of where those stacks are deployed,” she said “We do that by providing users the ability to model their infrastructure stacks from the base operating system-on-up in something called cluster profiles. We then manage the deployment and maintenance of those communities infrastructure stacks, deployed from cluster profiles, all from our SAS management system.”
Then, later in the show, we discuss some of the other top posts and podcasts of the week. We delve into error-monitoring in a podcast with Sentry’s Ben Vinegar. We revisit the debate of whether to use microservices or a monolithic architecture, or, more realistically, a mixture of both. We delve into the hidden powers of the Unix Sudo command, as well as touch upon what gear you would need to run a cloud native stack at home.