Kubernetes Architecture & Components
Overview
Kubernetes (K8s) is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It follows a master-worker node architecture for control and execution.
Core Architecture
Kubernetes architecture consists of two main layers:
✓ Control Plane (Master Node) – Manages and controls the entire cluster.
✓ Worker Nodes – Execute workloads and run containerized applications (Pods).
Control Plane Components
1. API Server
✓ Central access point for all Kubernetes components.
✓ Exposes the Kubernetes API to handle REST requests.
✓ Validates and processes commands from kubectl and other components.
2. etcd
✓ A distributed key-value store maintaining cluster configuration and state.
✓ Ensures high availability and consistency of cluster data.
✓ Used as the single source of truth for all cluster information.
3. Controller Manager
✓ Runs background controllers to maintain cluster state.
✓ Includes Node Controller, Replication Controller, and Endpoint Controller.
✓ Ensures the desired state of objects matches the actual state.
4. Scheduler
✓ Assigns newly created Pods to suitable worker nodes.
✓ Uses resource metrics and policies for intelligent scheduling.
✓ Ensures balanced workload distribution.
5. Cloud Controller Manager
✓ Integrates Kubernetes with cloud provider APIs.
✓ Manages cloud-specific tasks like load balancing and node management.
✓ Separates cloud logic from the core Kubernetes system.
Worker Node Components
1. Kubelet
✓ Agent running on every node that communicates with the API Server.
✓ Ensures containers in Pods are running correctly.
✓ Reports node and Pod status to the control plane.
2. Kube Proxy
✓ Maintains networking rules across nodes.
✓ Handles Pod-to-Pod and external communication.
✓ Implements load balancing within the cluster.
3. Container Runtime
✓ Executes and manages containers in Pods.
✓ Common runtimes include Docker, containerd, and CRI-O.
✓ Pulls container images and handles low-level operations.
Additional Concepts
Pods
✓ Smallest deployable unit containing one or more containers.
✓ Shared storage and network resources.
ReplicaSets
✓ Maintains the desired number of Pod replicas.
✓ Ensures high availability and fault tolerance.
Deployments
✓ Provides declarative application updates.
✓ Simplifies scaling, rollback, and rollout processes.
Services
✓ Abstracts access to a set of Pods.
✓ Provides stable networking endpoints within or outside the cluster.
ConfigMaps & Secrets
✓ Store configuration and sensitive data securely.
✓ Separate configuration from application code.
Namespaces
✓ Logical segmentation for resource isolation and organization.
✓ Useful in managing large clusters and multi-tenant environments.
Tip
Kubernetes architecture harmonizes the Control Plane (for management) and Worker Nodes (for execution). Together, they automate the deployment, scaling, networking, and health of containerized workloads efficiently and reliably.
Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been released and with it comes brand new Cloud Management Platform – VCF Automation (VCFA) which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Comments
Post a Comment