<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vinod Kumar on Medium]]></title>
        <description><![CDATA[Stories by Vinod Kumar on Medium]]></description>
        <link>https://medium.com/@vinod5b9?source=rss-2a4f8df5b68a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Vinod Kumar on Medium</title>
            <link>https://medium.com/@vinod5b9?source=rss-2a4f8df5b68a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:09:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinod5b9/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Demystifying the Kubernetes Architecture]]></title>
            <link>https://medium.com/@vinod5b9/demystifying-the-kubernetes-architecture-215e61e10eaa?source=rss-2a4f8df5b68a------2</link>
            <guid isPermaLink="false">https://medium.com/p/215e61e10eaa</guid>
            <dc:creator><![CDATA[Vinod Kumar]]></dc:creator>
            <pubDate>Tue, 11 Jun 2024 12:17:53 GMT</pubDate>
            <atom:updated>2024-06-11T12:17:53.235Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Introduction</strong></blockquote><p>Kubernetes has emerged as the leading container orchestration platform, providing a powerful and flexible infrastructure for deploying, scaling, and managing containerized applications. At the heart of Kubernetes lies its architecture, which comprises several key components distributed across master and worker nodes. In this article, we’ll delve into the intricacies of the Kubernetes architecture to gain a deeper understanding of how it orchestrates containerized workloads.</p><blockquote><strong>Kubernetes Cluster Overview</strong></blockquote><p>A Kubernetes cluster consists of one or more master nodes and multiple worker nodes. The master nodes are responsible for managing the cluster’s state and orchestrating tasks, while the worker nodes execute the workload.</p><blockquote><strong>Master Node Components</strong></blockquote><p>The master node hosts several essential components:</p><ol><li><strong>API Server:</strong> The API server acts as the front-end for the Kubernetes control plane. It exposes the Kubernetes API, which allows users to interact with the cluster, manage resources, and perform administrative tasks.</li><li><strong>Controller Manager:</strong> The controller manager is responsible for managing various controllers that regulate the state of the cluster. These controllers include the Node Controller, Replication Controller, Endpoints Controller, and Service Account Controller, among others.</li><li><strong>Cloud Controller Manager:</strong> The cloud controller manager interacts with the cloud provider’s API to manage resources such as load balancers, storage volumes, and virtual machines. It abstracts cloud-specific functionality from the core Kubernetes components.</li><li><strong>Scheduler:</strong> The scheduler is responsible for placing pods onto suitable nodes in the cluster based on resource requirements, affinity, anti-affinity policies, and other constraints.</li><li><strong>etcd:</strong> etcd is a distributed key-value store that serves as the cluster’s primary data store. It stores configuration data, state information, and metadata about the cluster’s resources.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kKGQ9GTMwHoHWFy20t-zkw.png" /><figcaption>Kubernetes Architecture</figcaption></figure><blockquote><strong>Worker Node Components</strong></blockquote><p>The worker nodes are where the application containers are scheduled and executed. Each worker node typically consists of the following components:</p><ol><li><strong>Kubelet:</strong> The kubelet is an agent that runs on each worker node and is responsible for managing the lifecycle of pods. It interacts with the API server to receive pod specifications, pull container images, and start/stop containers as necessary.</li><li><strong>Kube-Proxy:</strong> Kube-proxy is a network proxy that runs on each worker node and maintains network rules to enable communication between pods and services within the cluster. It facilitates load balancing and service discovery.</li><li><strong>Container Runtime:</strong> The container runtime is the software responsible for running containers. Kubernetes supports various container runtimes, including Docker, containerd, and CRI-O. It manages the execution of containerized applications, handling tasks such as image management, container lifecycle, and resource isolation.</li></ol><blockquote><strong>Conclusion</strong></blockquote><p>In summary, comprehending the Kubernetes architecture is fundamental to proficiently managing containerized workloads within a cluster. By exploring the roles and responsibilities of each component within the master and worker nodes, we’ve uncovered the intricate orchestration capabilities that Kubernetes offers. However, this exploration is merely scratching the surface of Kubernetes potential. In the upcoming sequel, we will delve deeper into the dynamic interactions among these components during deployments. Stay tuned for our in-depth examination of component interactions — a pivotal aspect of mastering Kubernetes. Your journey continues!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=215e61e10eaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>