Would you like to know what is Kubernetes?
Why it was created and why we use it?
If so, this video is for you?
Hi, my name is Michael Gibbs, and I'm the founder and CEO Go Cloud careers.
And we're an organization that's dedicated towards building most high performance cloud
computing careers.
Personally, I've been working in tech now for over 25 years.
And I've been helping others get their first tech job or get promoted in tech for more
than two decades.
And I want to help you get cloud hired and get your first tech job.
In this video, we're going to talk about what is Kubernetes, we're going to cover it from
a high level.
To give you a quick and brief introduction to Kubernetes.
We will go over some of the Kubernetes concepts we will talk about why it was created, what
problems it solves, we'll look briefly into the Kubernetes architecture.
And then we're even going to discuss the interplay between Docker and Kubernetes.
As we know, there's a lot of confusion there.
So what is Kubernetes Kubernetes is an open source container orchestration platform by
orchestration.
It's the control plane that determines how and where the containers are going to be scaling,
growing, operating, etc.
Now, Kubernetes was originally developed by Google.
And it's open source, which means we can use it in our data centers and all clouds, which
makes us a ripe protocol for innovation, a great great, great technology.
And what happened is the Kubernetes orchestration will make sure the containers are where they're
supposed to be, and that all the containers are working together.
So why did we go down this path of Kubernetes, we used to have monolithic applications where
the whole application was on a single server back when I started, and when the server got
pilled, we got a bigger server.
And then we started to decouple our applications and started to use load balancers, we could
share the load across multiple servers.
And we decoupled them and saying perhaps we have a web tier and app tier and a database.
But we always run into a scaling issue, we always run into a capacity issue.
And as we add more technology, things change.
So it can be in a monolithic application that's got 10 Different parts of it, where a single
component is the bottleneck to the entire system.
And that single component can force us to need a whole lot more servers, when in reality,
all we need is just to scale that single component.
And that's where micro services come into play.
micro services are basically breaking down the application into little mini services,
and scaling out meaning adding a little capacity to a decent additional services as needed.
So that way, we can scale what the bottlenecks are, as opposed to the entire system, enabling
more efficient systems at a lower cost.
So micro services work by enabling the Kubernetes cluster, which is going to be looking at all
these micro services to say the capacity, this one's up, I had more or this service
stopped restarted with a new one,
let's talk about self healing and high availability.
Kubernetes dramatically promotes self healing and high ability.
But here's why.
When the Kubernetes cluster and deployment is set up, they might say I need 10 copies
of service a and if all of it on the Kubernetes orchestration is going to be looking at it
saying 10 copies of service a are running.
Now if one of the copies dies, guess what the Kubernetes master node is going to look
at this and say, Okay, we need to spin up another one, which is fantastic.
Likewise, we can actually look at the control plane side and see that the services are at
90 hydroxamic capacity, scale out those services, but not everything else.
So this is fantastic.
So you can see we've got self healing, we've got the ability to add more capacity on demand.
So how does Kubernetes work, and we're gonna basically take this at a high level, at the
top level, you've got the master node, the master node is the brain, it's the control
plane that determines what should be an were kind of like the conductor in an orchestra,
that tells people to play loud or play calm, are you gonna speed up slow down, that's what
the master node is doing.
Now, what will also happen in Kubernetes, is we're gonna have something called a pod.
And a pod is going to be a collection of containers that are going to be a virtual machine.
So you're gonna have at the top, you're gonna have your master node, and then you're gonna
have your virtual machines on your virtual machine.
That's where your Kubernetes pods are.
No, of course, we can put the pods in a serverless environment.
But let's assume we're working off of a virtual machine.
The next component we want to talk about in Kubernetes is basically a service and that's
kind of like a load balancer that distributes your traffic to the pods.
And it's a it's a software based load balancer.
That's part of it.
The next part of Kubernetes we should talk about is something called a deployment.
So when the DevOps engineer deploys Kubernetes they're gonna make a deployment file, it's
going to end in a dot yml Yamo file.
And this is where the developer the application is going to include the specification for
the deployment.
It'll usually include a replica set, which in turn tells them the number of containers
to use.
That's where all the magic happens.
have three of these when shuts down, and another one, three of these are busy.
Guess what?
Add more so wonder
Whoa, wonderful, wonderful.
Now there's another component called the cubelet.
And this is really a service that exists on the worker nodes.
These are the virtual machines where the pods are created, which communicates to the Kubernetes
cluster cluster.
So we talked about Kubernetes being a container orchestration platform.
And there's lots of places you can run your containers on it.
It doesn't have to be a Docker environment.
But what is Docker then?
Docker is a container runtime module.
So look at it this way, if you have an environment, and you can see in this graphic here, where
you have your server, then you've got your operating system.
Usually for containers, the Vironment, there's typically a bunch of Linux.
On top of that you've got a Container Engine such as Docker, and then you've got your containers
sitting on top of that.
So Docker is a container runtime module.
So how's the interplay between Docker and Kubernetes Kubernetes does the orchestration
of world of containers need to be and Docker enables the containers to run out like I said,
there's other versions other than Docker to enable containers to run in today's world.
But that's what Docker does.
Docker enables containers to run so is Kubernetes.
And either or with Docker, not really Kubernetes.
The manager, Docker is one of the potential container runtime modules that you can use.
So as you can see, Kubernetes is an open source framework, which means we can use them in
a hybrid cloud, multi cloud, a data center or a single cloud.
It's an open source framework.
So it enables and facilitates fantastic transformation.
Not just that it scales great and improves availability, and system performance.
I hope you've enjoyed this introductory video on what is Kubernetes.
What is Docker and the interplay between the two.
If you're looking to get your first cloud job, and you're not sure where to go, or you'd
like some guidance, we have a completely free how to get your first cloud architect job
on our every Thursday.
On this webinar, we will tell you the following How to get your first cloud architect job,
what hiring managers are looking for in a cloud architect, what should be on your resume,
how to bypass HR, so you can get caught hard when you don't have experience.
Additionally, if you're looking to build your cloud computing career, I am online free three
times a week on YouTube Mondays, Wednesdays and Fridays and you can ask me any type of
cloud computing career questions you have, maybe how to become a cloud architect how
to become a Solution Architect how to become a cloud engineer how to get the first cloud
architect job Solution Architect job or cloud engineer job, because I want to help you all
get cloud heart.
This is Michael Gibbs, and I look forward to seeing you in another video.
Take care