http://blog.ghanmi.me/tags/kubernetes/Recent content in Kubernetes on MLogHugo -- gohugo.ioen-usTue, 24 Mar 2026 01:38:01 +0100http://blog.ghanmi.me/posts/2-nodes-k8s-cluster-with-terraform-libvirt-and-ansible/Sun, 02 Feb 2025 00:00:00 +0000http://blog.ghanmi.me/posts/2-nodes-k8s-cluster-with-terraform-libvirt-and-ansible/What we are building Prerequisites The KVM host needs the following packages installed. Commands are for Debian/Ubuntu. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 # Virtualization stack sudo apt-get update sudo apt-get install -y \ qemu-kvm libvirt-daemon-system libvirt-clients \ bridge-utils virtinst virt-manager # Terraform (via HashiCorp APT repo) wget -O- https://apt.releases.hashicorp.com/gpg | \ sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.http://blog.ghanmi.me/posts/single-node-k8s-terraform-libvirt-ansible/Mon, 14 Oct 2024 00:00:00 +0000http://blog.ghanmi.me/posts/single-node-k8s-terraform-libvirt-ansible/Why This Stack? Running Kubernetes locally or in a homelab doesn’t require a cloud account. If you have a Linux host with KVM support, you can provision virtual machines with Terraform’s dmacvicar/libvirt provider, configure them with Ansible, and end up with a reproducible, single-node cluster that mirrors how you’d build real infrastructure. minus the cloud bill. This guide walks through every layer: host prerequisites, Terraform configuration, cloud-init bootstrapping, Ansible playbooks for kubeadm, and post-install verification.http://blog.ghanmi.me/posts/building-k8s-cni-plugin-with-ebpf/Tue, 03 Sep 2024 00:00:00 +0000http://blog.ghanmi.me/posts/building-k8s-cni-plugin-with-ebpf/Prerequisites A working Kubernetes cluster for testing (a single-node kind or kubeadm cluster works perfectly) clang/llvm for compiling eBPF programs, bpftool What We’re Building Our plugin will handle a single, well-defined scope: pod-to-pod connectivity on a single node. That means every pod gets an IP address, and any pod can reach any other pod on the same machine. We won’t handle multi-node routing, services, or network policy. each of those is a project unto itself.