Differences

This shows you the differences between two versions of the page.

--- products:ict:cloud_computing:kubernetes [2023/05/11 14:44] – wikiadmin
+++ products:ict:cloud_computing:kubernetes [2023/10/19 03:16] (current) – wikiadmin
@@ Line 1: / Line 1: @@
+Kubernetes, often abbreviated as K8s, is an open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications. It was originally developed by Google and is now maintained by the Cloud Native Computing Foundation (CNCF). Kubernetes has become the de facto standard for managing containerized applications in modern cloud-native environments. Here are some key aspects and components of Kubernetes:
+**Key Concepts:**
+. **Containerization**: Kubernetes is designed to work with containers, which are lightweight and consistent packaging units for applications and their dependencies. The most commonly used container runtime with Kubernetes is Docker.
+. **Cluster**: In Kubernetes, a cluster is a set of machines (nodes) that work together to run containerized applications. The cluster typically consists of a master node for control and multiple worker nodes for running containers.
+. **Nodes**: Worker nodes, often referred to as "minions," are physical or virtual machines that run containerized applications. Each node has a container runtime (e.g., Docker), the Kubernetes agent (kubelet), and other supporting components.
+. **Pods**: Pods are the smallest deployable units in Kubernetes. A pod can contain one or more containers that share the same network namespace and storage volume. Containers in the same pod can communicate with each other through `localhost`.
+. **ReplicaSets**: ReplicaSets are used to ensure that a specified number of pod replicas are running at all times. They help with scaling and maintaining the desired number of instances of an application.
+. **Services**: Kubernetes Services define a logical set of pods and policies for accessing them. They provide a stable network endpoint for connecting to the pods, regardless of changes in the underlying infrastructure.
+. **Namespaces**: Namespaces are a way to partition resources in a cluster. They provide a scope for organizing and isolating objects like pods, services, and volumes.
+**Control Plane:**
+. **Master Node**: The master node is the control plane of the Kubernetes cluster and manages the overall cluster state, including scheduling, scaling, and maintaining application availability.
+. **Kube-API Server**: This is the component of the master node that exposes the Kubernetes API and is responsible for receiving and processing requests from users and other components.
+. **Etcd**: A distributed key-value store that is used to store the configuration data for the entire cluster. It's the source of truth for all cluster data.
+. **Kube-Scheduler**: This component is responsible for scheduling pods to nodes based on resource requirements and constraints.
+. **Kube-Controller-Manager**: It manages different types of controllers that regulate the state of the system, such as ReplicaSets, Deployments, and Services.
+. **Cloud Controller Manager**: If the cluster is running in a cloud provider environment, this component manages interactions with the cloud provider's infrastructure.
+**Worker Nodes:**
+. **Kubelet**: This agent runs on each worker node and is responsible for communicating with the control plane and ensuring that containers are running in pods as expected.
+. **Container Runtime**: Kubernetes is designed to be container-agnostic, but Docker is one of the most commonly used container runtimes.
+. **Kube-Proxy**: Kube-Proxy maintains network rules on worker nodes to allow network communication to your pods from network sessions inside or outside of your cluster.
+**Kubernetes Ecosystem:**
+Kubernetes has a vast ecosystem of tools and extensions that complement its core functionality, including Helm (a package manager for Kubernetes), Istio (for service mesh), and Prometheus (for monitoring and alerting), among others.
+Kubernetes is a powerful and versatile platform for managing containerized applications. It simplifies many aspects of deploying and managing applications, making it a popular choice for organizations looking to build and scale container-based services.
 Welcome & Introduction