<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pod on marktaguiad.dev</title>
    <link>https://marktaguiad.dev/tags/pod/</link>
    <description>Recent content in Pod on marktaguiad.dev</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>marktaguiad@marktaguiad.dev (Mark Taguiad)</managingEditor>
    <webMaster>marktaguiad@marktaguiad.dev (Mark Taguiad)</webMaster>
    <copyright>marktaguiad.dev</copyright>
    <lastBuildDate>Fri, 06 Mar 2026 12:15:40 +0800</lastBuildDate>
    <atom:link href="https://marktaguiad.dev/tags/pod/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Controller</title>
      <link>https://marktaguiad.dev/post/k8s-notes-part5/</link>
      <pubDate>Fri, 06 Mar 2026 12:15:40 +0800</pubDate><author>marktaguiad@marktaguiad.dev (Mark Taguiad)</author>
      <guid>https://marktaguiad.dev/post/k8s-notes-part5/</guid>
      <description>&lt;p&gt;Kubernetes is designed to keep applications running even when failures occur. One of the key mechanisms that enables this is the Controller.&lt;/p&gt;&#xA;&lt;p&gt;Controllers continuously monitor the cluster and ensure that the actual state matches the desired state. If something goes wrong, Kubernetes automatically corrects it.&lt;/p&gt;&#xA;&lt;p&gt;This behavior is commonly referred to as self-healing.&lt;/p&gt;&#xA;&lt;p&gt;It performs three main tasks:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Observe the current state&lt;/li&gt;&#xA;&lt;li&gt;Compare it with the desired state&lt;/li&gt;&#xA;&lt;li&gt;Take action if they differ&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This loop runs continuously inside the Kubernetes control plane.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kubernetes Pod</title>
      <link>https://marktaguiad.dev/post/k8s-notes-part2/</link>
      <pubDate>Thu, 05 Mar 2026 17:22:20 +0800</pubDate><author>marktaguiad@marktaguiad.dev (Mark Taguiad)</author>
      <guid>https://marktaguiad.dev/post/k8s-notes-part2/</guid>
      <description>&lt;p&gt;&lt;img&#xA;  class=&#34;theme-image&#34;&#xA;  src=&#34;https://marktaguiad.dev/images/devops/k8s-notes/k8s-notes-pod-001.png&#34;&#xA;  data-light=&#34;/images/devops/k8s-notes/k8s-notes-pod-001.png&#34;&#xA;  data-dark=&#34;/images/devops/k8s-notes/k8s-notes-pod-dark-001.png&#34;&#xA;  alt=&#34;Architecture Diagram&#34;&#xA;&gt;&#xA;&#xA;In Kubernetes, you do not deploy containers directly. Instead, containers run inside a Pod, which acts as a wrapper around one or more containers. Pods are the smallest deployable unit in the Kubernetes.&lt;/p&gt;&#xA;&lt;p&gt;A Pod provides:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Shared specification for containers&lt;/li&gt;&#xA;&lt;li&gt;Shared storage (volumes)&lt;/li&gt;&#xA;&lt;li&gt;Shared network&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h1 id=&#34;table-of-contents&#34;&gt;Table of Contents&lt;/h1&gt;&#xA;&lt;nav id=&#34;TableOfContents&#34;&gt;&#xA;  &lt;ol&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#kubeconfig&#34;&gt;Kubeconfig&lt;/a&gt;&lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#creating-pods-with-kubectl&#34;&gt;Creating Pods with kubectl&lt;/a&gt;&lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#using-yaml-for-kubernetes-resources&#34;&gt;Using YAML for Kubernetes Resources&lt;/a&gt;&lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#multiple-pods&#34;&gt;Multiple Pods&lt;/a&gt;&#xA;      &lt;ol&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#manifest&#34;&gt;Manifest&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#namespace&#34;&gt;Namespace&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#deploy&#34;&gt;Deploy&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#listing-the-pod&#34;&gt;Listing the Pod&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#verify&#34;&gt;Verify&lt;/a&gt;&lt;/li&gt;&#xA;      &lt;/ol&gt;&#xA;    &lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#pod-lifecycle&#34;&gt;Pod Lifecycle&lt;/a&gt;&#xA;      &lt;ol&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#pending&#34;&gt;Pending&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#running&#34;&gt;Running&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#succeeded&#34;&gt;Succeeded&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#failed&#34;&gt;Failed&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#completed--terminated&#34;&gt;Completed / Terminated&lt;/a&gt;&lt;/li&gt;&#xA;      &lt;/ol&gt;&#xA;    &lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#pod-readiness-and-liveliness-probe&#34;&gt;Pod Readiness and Liveliness Probe&lt;/a&gt;&#xA;      &lt;ol&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#liveness-probe&#34;&gt;Liveness Probe&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#readiness-probe&#34;&gt;Readiness Probe&lt;/a&gt;&lt;/li&gt;&#xA;        &lt;li&gt;&lt;a href=&#34;#demo&#34;&gt;Demo&lt;/a&gt;&lt;/li&gt;&#xA;      &lt;/ol&gt;&#xA;    &lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#pods-are-ephemeral&#34;&gt;Pods Are Ephemeral&lt;/a&gt;&lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#clean-up&#34;&gt;Clean Up&lt;/a&gt;&lt;/li&gt;&#xA;    &lt;li&gt;&lt;a href=&#34;#bonus&#34;&gt;Bonus&lt;/a&gt;&lt;/li&gt;&#xA;  &lt;/ol&gt;&#xA;&lt;/nav&gt;&#xA;&lt;h3 id=&#34;kubeconfig&#34;&gt;Kubeconfig&lt;/h3&gt;&#xA;&lt;p&gt;Before we deploy pods, let&amp;rsquo;s first discuss &lt;code&gt;kubeconfig&lt;/code&gt; for cluster access. Check this &lt;a href=&#34;https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/&#34;&gt;link&lt;/a&gt; for further explanation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
