https://marktaguiad.dev/tags/csi/ Recent content in Csi on marktaguiad.dev Hugo en-us marktaguiad@marktaguiad.dev (Mark Taguiad) marktaguiad@marktaguiad.dev (Mark Taguiad) marktaguiad.dev Fri, 06 Mar 2026 03:32:32 +0800 https://marktaguiad.dev/post/k8s-notes-part4/ Fri, 06 Mar 2026 03:32:32 +0800marktaguiad@marktaguiad.dev (Mark Taguiad) https://marktaguiad.dev/post/k8s-notes-part4/ <p>Containers in Kubernetes are ephemeral by default. This means that when a container stops or a Pod is deleted, any data stored inside the container filesystem is lost.</p> <p>To solve this problem, Kubernetes provides Volumes, which allow data to persist and be shared between containers in a Pod.</p> <p>Volumes are mounted into containers and provide persistent or shared storage depending on the type used.</p> <h1 id="table-of-contents">Table of Contents</h1> <nav id="TableOfContents"> <ol> <li><a href="#how-volume-works">How Volume Works</a></li> <li><a href="#volume-types">Volume Types</a> <ol> <li><a href="#emptydir">emptyDir</a></li> <li><a href="#hostpath">hostPath</a></li> <li><a href="#persistentvolume-pv">PersistentVolume (PV)</a></li> <li><a href="#persistentvolumeclaim-pvc">PersistentVolumeClaim (PVC)</a></li> </ol> </li> <li><a href="#persistent-storage-architecture">Persistent Storage Architecture</a></li> <li><a href="#container-storage-interface">Container Storage Interface</a></li> </ol> </nav> <h3 id="how-volume-works">How Volume Works</h3> <p>Remember the first example we make, this time we will mount with different type of Kubernetes Volumes.</p> https://marktaguiad.dev/post/kubeadm-ansible/ Wed, 09 Jul 2025 00:00:00 +0000marktaguiad@marktaguiad.dev (Mark Taguiad) https://marktaguiad.dev/post/kubeadm-ansible/ <p>Over the years, I’ve found myself repeatedly setting up Kubernetes clusters using kubeadm—and while it works well, the manual process can get repetitive and error-prone. That’s why I built <a href="https://github.com/mcbtaguiad/kubeadm-ansible">kubeadm-ansible</a>: an Ansible playbook that automates the entire process of standing up a Kubernetes cluster.</p> <p>This project was born out of my desire for a simple, reusable way to deploy multi-node clusters quickly—especially in test environments, homelabs, and lightweight production setups.</p> <h1 id="table-of-contents">Table of Contents</h1> <nav id="TableOfContents"> <ol> <li><a href="#what-it-does">What It Does</a></li> <li><a href="#setup">Setup</a></li> <li><a href="#inventory">Inventory</a> <ol> <li><a href="#single-master-cluster">Single Master Cluster</a></li> <li><a href="#multi-master-cluster">Multi Master Cluster</a></li> <li><a href="#cluster-config">Cluster Config</a></li> </ol> </li> <li><a href="#init-cluster">Init cluster</a></li> <li><a href="#other-playbook">Other Playbook</a></li> <li><a href="#k3s">k3s</a></li> </ol> </nav> <h3 id="what-it-does">What It Does</h3> <p>kubeadm-ansible simplifies Kubernetes provisioning by:</p>