 Hey, y'all. My name is Amy. I am a software engineer at Rancher Labs. And I actually started there in March and learned about this crazy new thing called containers and Kubernetes. So I'm going to attempt to talk to you about it within five minutes. So obviously, it can't go into too much technical detail, but I'll try to give you a good start and good overview overall. So the idea is that you want to be able to abstract away your infrastructure so that application developers can just release their code into the cloud, whatever that means. It's sort of this really big term that just means a bunch of servers. So at the core of Kubernetes is containers. And the way I can describe containers are that they're a baby computer inside another computer, the baby computer being your container, and the other computer being the server. So you may be wondering why would I want to do this. So the idea is that it provides great resource isolation. It also allows you to utilize your server more efficiently. And the main thing is that it abstracts away your infrastructure, which is more clear here. So now what we're going to do is pretend I'm an application developer. So the main idea is I, as an infrastructure software engineer, do not need to trust you as a developer. So we want to build in failure into our infrastructure sort of orchestrator. So what we're doing now is we're putting an application inside a baby computer. So on your left there is sort of a pictorial representation of what's happening. So locally, you're developing. You have all these versions and operating system differences that you don't want to deal with when you are developing into production. So here I have Alpine 3.6.2, Python 3.7, and then I have a bunch of setup scripts. And what I'm doing is I'm copying my application binary into my container. And I'm exposing port 80 to expose my baby computer to the entire world. You can't just depend on just sort of leaving your baby computer and just plopping into the server. Your baby computer is going through this existential crisis. It's asking questions like, where should I live? This is under the realm of scheduling. How do I talk to other containers? That's under the realm of networking. How do I talk to the world? So how do I route traffic to my baby computer? What happens if I get sick? And this is where Kubernetes comes in. So Kubernetes, I like to think of this as sort of like organizational abstraction on top of containers. All it's doing is it's organizing baby computers. The first abstraction is we have a pod. And what this is is a scheduling unit. And all this means is that a pod consists of one or more containers. And all of the pods, they are scheduled onto one node or one server. And they're always coupled together. So they depend on each other. And one pod is reached through an IP address. A deployment is one or more pods. And the idea is you have this idea of actual versus desired state, where let's say have a deployment of three. What I want to be able to do is to always make sure that three pods are up and running. Then I have something called services, where let's say you want to group together deployments or pods. And you want to always be able to reach them via an address within your cluster. So we can have something called service A or service B or front end and back end. And they'll always be able to reach each other within the cluster. And the final component of Kubernetes is called an ingress controller. And so what this is is that external traffic from the internet is able to reach to your baby computer within the cluster. So you'll have some sort of endpoint like foo. It'll reach service A through the endpoint foo. Service A will then route traffic to your deployments or pods within that service. And now we have a bunch of email files that basically just is the photo beforehand. So we have a deployment, we have a service, and we have an ingress controller. And I hope that you have a good foundational basis now for what Kubernetes is. Once again, it's just basically a way to organize all of your baby computers together. So thank you so much for your time. And allowing me to tell you about Kubernetes within five minutes. Yeah.