<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>K3s on Chetan&#39;s Portfolio</title>
    <link>https://chetan-thapliyal.cloud/tags/k3s/</link>
    <description>Recent content in K3s on Chetan&#39;s Portfolio</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Chetan Thapliyal</copyright>
    <lastBuildDate>Thu, 19 Nov 2026 11:06:47 +0530</lastBuildDate><atom:link href="https://chetan-thapliyal.cloud/tags/k3s/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Disaster Recovery You Can Point To: What Each Drill Proved, and What It Didn&#39;t</title>
      <link>https://chetan-thapliyal.cloud/posts/homelab-disaster-recovery-drills/</link>
      <pubDate>Thu, 19 Nov 2026 11:06:47 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/homelab-disaster-recovery-drills/</guid>
      <description>Five written recovery plans for a GitOps homelab, scored by what was actually drilled: a cold restore from the offsite copy with the API up in 54 seconds, app restores checked row by row, an offsite copy that root can&amp;rsquo;t delete, and an honest list of what hasn&amp;rsquo;t been tested yet.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-disaster-recovery-drills/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-disaster-recovery-drills/featured.png" />
    </item>
    
    <item>
      <title>Sizing Kubernetes on a 12 GB Laptop: What the Scheduler Sees and What&#39;s Really There</title>
      <link>https://chetan-thapliyal.cloud/posts/k3s-memory-sizing-12gb-laptop/</link>
      <pubDate>Thu, 19 Nov 2026 11:00:41 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/k3s-memory-sizing-12gb-laptop/</guid>
      <description>Live numbers from a three-node K3s cluster on a 12 GB laptop: requests, limits and real usage per node, the control plane the scheduler can&amp;rsquo;t see, the limits that OOM kills corrected, and the gap I found while writing this (nothing reserved for the OS, no memory eviction at all) with the same-day fix.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/k3s-memory-sizing-12gb-laptop/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/k3s-memory-sizing-12gb-laptop/featured.png" />
    </item>
    
    <item>
      <title>Observability Off the Cluster: Prometheus and Loki in the Cloud, One Agent per Node</title>
      <link>https://chetan-thapliyal.cloud/posts/homelab-observability-off-cluster-loki-alloy/</link>
      <pubDate>Thu, 19 Nov 2026 10:29:27 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/homelab-observability-off-cluster-loki-alloy/</guid>
      <description>My homelab&amp;rsquo;s monitoring runs on a free cloud VM, not on the cluster it watches. Why the split, what each node runs, the memory budget that turned out wrong, swapping Promtail for Grafana Alloy without a gap, and the alerts that watch the monitoring itself.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-observability-off-cluster-loki-alloy/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-observability-off-cluster-loki-alloy/featured.png" />
    </item>
    
    <item>
      <title>From Docker Compose to Kubernetes: Moving My First Apps, Platform First</title>
      <link>https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/</link>
      <pubDate>Thu, 19 Nov 2026 10:18:46 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/</guid>
      <description>Three self-hosted apps moved from Docker Compose on a cloud VM to my K3s cluster in one day. The platform they needed first, the guardrails every app inherits, how each Compose line became a Kubernetes object, what a read-only root filesystem broke, and the row counts that proved each move.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/featured.png" />
    </item>
    
    <item>
      <title>Homelab Kubernetes Storage: Why local-path Beat Longhorn and Ceph</title>
      <link>https://chetan-thapliyal.cloud/posts/homelab-kubernetes-storage-local-path-vs-longhorn/</link>
      <pubDate>Mon, 16 Nov 2026 12:39:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/homelab-kubernetes-storage-local-path-vs-longhorn/</guid>
      <description>Most Kubernetes guides reach for Longhorn or Rook-Ceph. On three VMs that share one laptop and one SSD, replication buys nothing and costs a third of the RAM. Why K3s&amp;rsquo;s local-path is the default here, what it gives up, and the two things it means for backups.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-kubernetes-storage-local-path-vs-longhorn/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/homelab-kubernetes-storage-local-path-vs-longhorn/featured.png" />
    </item>
    
    <item>
      <title>Gateway API on a Homelab: Envoy Gateway, MetalLB and an Internal CA on K3s</title>
      <link>https://chetan-thapliyal.cloud/posts/gateway-api-envoy-gateway-metallb-k3s/</link>
      <pubDate>Mon, 16 Nov 2026 12:30:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/gateway-api-envoy-gateway-metallb-k3s/</guid>
      <description>Why I disabled K3s&amp;rsquo;s Traefik and ServiceLB and built the cluster&amp;rsquo;s edge on Gateway API with Envoy Gateway, MetalLB and cert-manager. The setup, six things that broke on the way, and a root CA that would have re-keyed itself on Christmas Day.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/gateway-api-envoy-gateway-metallb-k3s/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/gateway-api-envoy-gateway-metallb-k3s/featured.png" />
    </item>
    
    <item>
      <title>Seven Silent GitOps Gotchas: What ArgoCD and Helm Didn&#39;t Tell Me</title>
      <link>https://chetan-thapliyal.cloud/posts/seven-silent-gitops-gotchas-argocd-helm/</link>
      <pubDate>Mon, 16 Nov 2026 12:20:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/seven-silent-gitops-gotchas-argocd-helm/</guid>
      <description>Settings Helm accepted and ignored, apps that read Healthy while ArgoCD had stopped managing them, a webhook that refreshed everything at once, and four more ways a GitOps setup can look fine while it isn&amp;rsquo;t. Each one with its evidence and the check that catches it now.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/seven-silent-gitops-gotchas-argocd-helm/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/seven-silent-gitops-gotchas-argocd-helm/featured.png" />
    </item>
    
    <item>
      <title>Building the GitOps Engine: ArgoCD, App-of-Apps, and Sync Waves That Didn&#39;t Wait</title>
      <link>https://chetan-thapliyal.cloud/posts/argocd-app-of-apps-sync-waves/</link>
      <pubDate>Mon, 16 Nov 2026 11:50:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/argocd-app-of-apps-sync-waves/</guid>
      <description>How Project Aether&amp;rsquo;s cluster builds itself from one root Application, why my sync waves ordered creation but not readiness, and the layer ArgoCD can&amp;rsquo;t manage that drifted from Git for three weeks.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/argocd-app-of-apps-sync-waves/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/argocd-app-of-apps-sync-waves/featured.png" />
    </item>
    
    <item>
      <title>Building My K3s Homelab: Creating a Proxmox Cloud-Init Template</title>
      <link>https://chetan-thapliyal.cloud/posts/proxmox-cloud-init-template-for-k3s-homelab/</link>
      <pubDate>Wed, 30 Sep 2026 22:00:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/proxmox-cloud-init-template-for-k3s-homelab/</guid>
      <description>How I built a reusable Ubuntu 24.04 cloud-init template on Proxmox VE to power my k3s homelab: one golden image to clone them all.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/proxmox-cloud-init-template-for-k3s-homelab/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/proxmox-cloud-init-template-for-k3s-homelab/featured.png" />
    </item>
    
  </channel>
</rss>
