Kubernetes Introduction

This article offers a concise introduction to key Kubernetes concepts, contrasting it with Docker while highlighting its advanced orchestration capabilities. Whether you are just starting out or looking to expand your infrastructure knowledge, this guide covers the basics, architectural components, and essential commands.

Running Applications: Docker vs. Kubernetes

When using Docker, you can run a single instance of an application using a straightforward command:

docker run my-web-server

Kubernetes, on the other hand, enables seamless scaling. For instance, the following command deploys a thousand instances simultaneously:

kubectl run --replicas=1000 my-web-server

Beyond simple scaling, Kubernetes supports dynamic adjustments—up to two thousand instances with another command. It also facilitates rolling upgrades, allowing you to update one instance at a time, and includes a rollback mechanism if issues arise. Moreover, Kubernetes enables you to experiment with new features by upgrading only a subset of instances using A/B testing methodologies.

Below is an example demonstrating Kubernetes' rolling update and scaling features:

docker run my-web-server
kubectl rolling-update my-web-server --rollback
kubectl rolling-update my-web-server --image=web-server:2
kubectl scale --replicas=2000 my-web-server

Kubernetes Architecture Overview

Kubernetes leverages container runtimes like Docker, Rocket, or CRI-O to execute applications within isolated containers. A Kubernetes cluster consists of multiple nodes managed by a master node that orchestrates containerized applications.

Nodes

Nodes are physical or virtual machines running Kubernetes software. They act as workers where containers are deployed. A typical Kubernetes cluster includes multiple nodes to guarantee high availability; if one node fails, the remaining nodes continue to operate, ensuring uninterrupted service.

Master

The master node runs the control plane components that manage and monitor the state of the cluster. Its responsibilities include maintaining cluster health, monitoring nodes, and reallocating workloads in the event of node failures.

When installing Kubernetes, the following core components are set up:

• API Server: Serves as the primary interface for all administrative tasks. It allows users, management devices, and CLI tools to communicate with the Kubernetes cluster.
• etcd: A distributed and reliable key-value store that contains all cluster data, ensuring consistency across multiple nodes.
• Scheduler: Responsible for distributing newly created containers across available nodes.
• Controllers: Detect changes in the cluster (like node failures or container issues) and initiate corrective actions by deploying new containers as needed.
• Container Runtime: The underlying software (e.g., Docker) that runs containers.
• kubelet: An agent that runs on each node to ensure containers operate as expected.

The diagram below illustrates these components and their interactions:

The kubectl Command-Line Tool

kubectl is the essential CLI tool for deploying and managing applications on a Kubernetes cluster. It is also used for retrieving critical cluster-related information, such as node status. Some basic commands include:

kubectl run hello-minikube
kubectl cluster-info
kubectl get nodes

These commands deploy an application, display cluster details, and list all nodes within the cluster. Additionally, you can deploy more complex applications. For example, to launch an application with 100 replicas, use:

kubectl run my-web-app --image=my-web-app --replicas=100

Conclusion

In this article, we provided a brief overview of Kubernetes, contrasting it with Docker while delving into its architecture and key management commands. For those interested in advancing from beginner basics to expert proficiency, consider exploring our comprehensive Kubernetes for the Absolute Beginners - Hands-on Tutorial.

Transcribed by https://otter.ai