Transcript
Newcomer: Given the mix in the audience, I'll try and do a little bit of both, some conversation about containers and Kube and not just assume you have full knowledge, but let's see how that goes.
Containers have absolutely exploded across the industry, and I work with many customers who have adopted containers and are using Red Hat's OpenShift container platform, which is built on Kubernetes. We've been partnering with the Kubernetes community for about four-plus years now or so - very excited to be part of that community. One of the key values of containers over deploying your apps simply on VMs is that you get to package all of the system dependencies that are required for that application to work in your container. Everything travels together, and that makes it much easier to ensure that, as your application moves from development to test to production, nothing changes, except maybe some of the secrets you're using to communicate with databases. It also makes it easier to put more applications on the same server, because you don't have to worry about conflicting system dependencies when you're using containers, and that's one of the reasons why they've become so popular.
Of course, enterprise apps rarely are going to be delivered in a single container. This is especially true if you're building microservice-based applications, where you have multiple services, each in their own container. They need to talk to each other, they need to discover each other. They need to be spun up when they're needed, and ideally, spun down when they're not needed. All of that is what you need a container orchestration engine for, and Kubernetes has really taken the orchestration world by storm. It's about three years ago that ..
Support the originator by clicking the read the rest link below.
