<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on Vivek&#39;s Blog</title>
    <link>https://www.codevivek.com/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Vivek&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>viveklp1995@gmail.com (Vivek Singh)</managingEditor>
    <webMaster>viveklp1995@gmail.com (Vivek Singh)</webMaster>
    <lastBuildDate>Fri, 11 Oct 2024 11:39:43 +0530</lastBuildDate>
    <atom:link href="https://www.codevivek.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deconstructing Kubernetes Scheduling Mechanisms</title>
      <link>https://www.codevivek.com/deconstructing-kubernetes-scheduling-mechanisms/</link>
      <pubDate>Thu, 10 Oct 2024 13:57:40 +0800</pubDate><author>viveklp1995@gmail.com (Vivek Singh)</author>
      <guid>https://www.codevivek.com/deconstructing-kubernetes-scheduling-mechanisms/</guid>
      <description>&lt;h3 id=&#34;deconstructing-kubernetes-scheduling&#34;&gt;Deconstructing Kubernetes Scheduling&lt;/h3&gt;&#xA;&lt;p&gt;Think of Kubernetes as a super-organized logistics manager. Its job? To ensure every Pod finds the perfect node to live on, based on its requirements, preferences, and constraints.&lt;/p&gt;&#xA;&lt;p&gt;But Kubernetes isn&amp;rsquo;t just about making sure the Pod &amp;ldquo;finds a place.&amp;rdquo; It uses sophisticated scheduling mechanisms like affinity, anti-affinity, taints, tolerations, and even direct assignments with &lt;code&gt;nodeName&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s dive into how Kubernetes works its scheduling magic. Before we start with that, lets just get a brief idea on how the api server decides which node the application should be deployed into.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deconstructing a Kubernetes Deployment</title>
      <link>https://www.codevivek.com/deconstructing-a-kubernetes-deployment/</link>
      <pubDate>Mon, 23 Sep 2024 13:57:40 +0800</pubDate><author>viveklp1995@gmail.com (Vivek Singh)</author>
      <guid>https://www.codevivek.com/deconstructing-a-kubernetes-deployment/</guid>
      <description>&lt;h1 id=&#34;deconstructing-a-kubernetes-deployment&#34;&gt;Deconstructing a Kubernetes Deployment&lt;/h1&gt;&#xA;&lt;p&gt;Think back to the first time you laid eyes on a Kubernetes deployment manifest. Did it make any sense to you apart from the &lt;code&gt;image&lt;/code&gt; and &lt;code&gt;container&lt;/code&gt; parameters? Wait, it did? Well, that makes one of us!&lt;/p&gt;&#xA;&lt;p&gt;When I first saw a Kubernetes deployment, I was hit with a flurry of questions. Questions that made me feel like I had opened the Matrix. Now, after some much-needed experience (and a few existential crises), I think I can finally answer some of those burning questions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Just Enough Kubernetes: Architecture</title>
      <link>https://www.codevivek.com/just-enough-kubernetes/</link>
      <pubDate>Sat, 10 Sep 2022 13:57:40 +0800</pubDate><author>viveklp1995@gmail.com (Vivek Singh)</author>
      <guid>https://www.codevivek.com/just-enough-kubernetes/</guid>
      <description>&lt;h1 id=&#34;tldr&#34;&gt;TLDR&lt;/h1&gt;&#xA;&lt;p&gt;Kubernetes is a container orchestration tool in which you can use multiple machines/VM’s to create a cluster. When cluster is created, application deployed on it are distributed throughout the nodes and Kubernetes makes sure they are up and available depending on the provided configuration.&lt;/p&gt;&#xA;&lt;h2 id=&#34;architecture&#34;&gt;Architecture&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Node&lt;/strong&gt;: A physical machine or VM where our applications are run when deployed.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Cluster&lt;/strong&gt;: A combination of nodes running together. It is best practice to have multiple nodes running at the same time to avoid a failure if any one of the nodes in the cluster stops working.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
