Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
30 views

What Is Kubernetes, and Why Do I Need It?

Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery called pods. Pods have a shared IP address and port space and can communicate easily. Kubernetes uses a master node to manage a pool of worker nodes where pods are deployed. It ensures that the deployed applications are running and available as required.

Uploaded by

Stephen Efange
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
30 views

What Is Kubernetes, and Why Do I Need It?

Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery called pods. Pods have a shared IP address and port space and can communicate easily. Kubernetes uses a master node to manage a pool of worker nodes where pods are deployed. It ensures that the deployed applications are running and available as required.

Uploaded by

Stephen Efange
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What Is Kubernetes, and Why Do I Need It?

So what are the problems that Kubernetes solves?

Well, the first thing is, Kubernetes has a master node and worker nodes (used to be called minions but
now they're worker nodes, slave nodes).

Kubernetes deploys what's called a pod, and the smallest unit in Kubernetes is the pod.

The pod is what holds the IP address, so all the containers in the pod have the same IP address.

This means if this is my database container and this is my Web container, it can see it on local host at
the port it's supposed to be on because all the pods in the container are the same IP address.

Now, pods can have one container or they can have multiple containers in logical groups.

It depends on how you want to build your pods, how you want to put the containers together.

Pods have some other features like shared volumes.

All the pods sharing IP space and all of the pods in the same cluster are all on the same IP space. And so
if this one is 2, this is 3, this is 4, 5, 6, 7, 8, all the same IP space if they're in the same cluster.

All the containers can communicate with all the other containers, so the container over here can talk to
the container over here.

Just ask the node's IP address, and we'll get into DNS and service discovery later. All the nodes could
communicate with all the other containers and all the other nodes and all the other pods on the whole
cluster. The IP the container sees itself as is the IP everybody sees it as. This is all facilitated by a network
overlay which there's a whole bunch of different choices you can make: Flannel, Weave Net, Istio. Use a
network overlay to do your IP management. Everything gets stored in etcd, which is a key value store for
the cluster so that all of your objects have metadata in there that can be referred to. And then you have
a kubelet that runs on all of the nodes, the master node, the worker nodes, all of them that make sure
that your cluster state is the state that you've assigned it. So the next step we're going to make is we're
going to install the kubernetes cluster, get everything up and running in a ready state, and then we'll
start looking at what is the difference between a master and a node? What do pods consist of? How do
we create pods and describe them? Let's put some DNS on it. What does DNS do? Let's look at that
network overlay and see how that's implemented what changes it makes. And then we'll start looking at
replica sets, services, and deployments to give you a quick overview, a real fast burn through how to get
a full-fledged

Kubernetes cluster up and running. In the end, I'm gonna have a hands-on lab that'll let you get one up
and running, too. But this is a quick start. There are some more in-depth courses out there that are
going to answer a bunch of questions that might get raised in this. We're going to go kind of fast, and I'm
going to skip over some stuff because this is just the quick start. This is just to get your feet wet and get
you familiar with it. If you're interested in this stuff at the end of this course, I totally recommend that
you go and continue learning, and we'll talk about that when I get to the last video in the course. But for
now, my name is Mike, this is Linux Academy. Thanks for watching.

You might also like