Kubernetes (K8S) introduction

-



So, by now chances are you have heard about Kubernetes at least ones. In this article, we will try to demystify Kubernetes and transform this buzzword into something we can comprehend.
To those of you that didn't get a chance to read one of my previous articles introducing the key concepts of Docker, (Who are you, Docker?) I strongly suggest you start by reading that article before you move forward to this one.

So what is Kubernetes?
Kubernetes, (commonly stylized as K8s) is an open source originally designed by Google. It is a container orchestration system for automating application deployment, scaling, and management.

Cluster who? -  Terminology that will help us move forward.
For one let's understand what is a cluster.
If you ever played around with Docker containers you must know how easy it is to spin up several Containers or multi-container applications. Maybe you even got a chance to experiment with docker-compose.  For something very small this kind of deployment could be sufficient, but sometimes you have complex architectures that go way beyond a hand-full of Containers that you can keep track of in your mind. There are complex deployments that could include multiple Containers on multiple servers. This kind of Container-based architecture is called a Cluster. So, how would we go from 5 servers to 50? how would you remember or keep track of on which machine you launched, for example, your Redis server? how would you manage this kind of scale?

Basic Kubernetes Skeleton (Architecture)
On a very high level, These are the key components in Kubernetes.
First, you have a "master node". A "master node" is a process and it manages the cluster.
There are also "Worker nodes". The worker nodes are basically machines (Both physical or virtual) that combine the cluster architecture. There can be more than one Master nodes and obviously, there can be thousands of Worker nodes.
The worker nodes contain "Pods". The pods are basically a scheduled unit. It could be one or more Containers. With the help of these "Pods", we can deploy multiple dependant containers together.
You can say that the pod acts as a wrapper around these Containers.
The master's role in all of this super cool structure is to manage and monitor the cluster and its components.
Kubernetes keeps track of it's deployed components and has monitoring mechanism. It performs a "health check" on them and knows when something fails.
One more important component in Kubernetes is the API server. The API server is the gateway to the entire Cluster. If we want to create, display, delete or update any Kubernetes object, you have to go through this API.






3 main things Kubernetes simplifies for us:

 Deployment - With this type of orchestration tool, scaled deployments are made easier.

 Scaling - It is reasonable to assume that you do not spin up a server each time you want to deploy a container. That is just not a reasonable way to manage your resources. Well, in this case, Kubernetes will "Find" the best place for your Pods given their CPU and other sustainable requirements.

 Monitoring - As we mentioned, monitoring a huge Cluster is not a simple task. With Kubernetes and its built-in Monitoring mechanism, we can better control our architecture.

This is obviously a high-level introduction to K8s. You can visit Kubernetes.io for more helpful information.





קורס אוטומציה למתקדמים - ההרשמה נפתחה למחזור ספטמבר
:פרטים בלינק







Comments

Post a Comment

Popular posts from this blog

Sharing is caring - Intro to Jenkins shared libraries

-
Image
  Whether you're just dipping your toes into the world of automation infrastructure, or already crafting your first jobs to automate your test execution, Jenkins is your new best friend.  In this blog post, we will talk a bit more about the practice of infrastructure as code, its relevance to test automation, and how you can avoid code duplications, align with industry best practices, and enable velocity, maintainability, and collaboration. So, whether you're a seasoned pro or just starting out, let's dive into the world of Jenkins Shared Libraries and see how they can make your life easier. Jenkins Shared Libraries play a crucial role in the realm of Infrastructure as Code (IaC).  So, what are they exactly? Think of Jenkins Shared Libraries as your secret stash of code snippets, neatly organized and ready to be plugged into your pipelines whenever needed. Let's explore the aspect of reusability within Jenkins Shared Libraries: Reusability is the cornerstone of efficien...
Read more

Intro to Terraform and how it is related to test automation infrastructure

-
Image
In this post, we will take a closer look at one of the most popular infrastructure-as-code software tools developed by HashiCorp, and if you follow my recent content, that name should start ringing a few bells. So, what is Terraform and why do we need it? Terraform allows you to define and describe your infrastructure in the form of code. To be more specific “HashiCorp declarative configuration language” (or HCL in short). With Terraform you can manage your resources and infrastructure modules like servers, VPCs, security groups, and much more, even if they are located on different providers such as AWS or Azure.  Generally speaking, cloud providers have their own infrastructure-as-code tools like CloudFormation or ARM. But, Terraform has very extensive support for different cloud providers and platforms allowing you to use a single tool for cross-cloud configurations. This makes it easier to manage your resources, easier to onboard and this is a scalable and in general, the “best ...
Read more

Test Automation, Security, and other vegetables

-
Image
Automation, Security, and other vegetables What is commonly overlooked when focusing on Quality? In this blog post, I want to delve into an aspect commonly overlooked in the context of Test Automation, and that’s the Security aspect.  As test automation developers, we often overlook the basic fact that we are working on a software project. Just like any other software project, considering security in our test automation practices adds a vital layer of protection to our work environment and helps ensure that our work which was initially meant to save time and help quality efforts, will not provide an easy and accessible breach point to our application.  So, on this note, let’s dive into why security should be an integral part of our automation efforts and explore some strategies to ensure our project is as effective as it is secure.  Analyze the attack surface - Before we can effectively secure our test automation infrastructure, it's crucial to identify and analyze poten...
Read more