Talos is a modern, minimal, and secure Kubernetes operating system designed for production environments, focusing on immutability and API-driven management for enhanced security and reliability.
View All Tags
Welcome to part 3 of the Talos Linux Kubernetes cluster bootstrap of the Proxmox series. In today's post, we will perform changes to make the code reusable and extensible. Users can follow a GitOps approach towards Talos deployments.
We assume you already have the basic project structure. To follow along, check out the part 1 and part 2 posts.
Welcome to part 2 of the Talos Linux Kubernetes cluster bootstrap on the Proxmox series.
We will enable Cilium as our CNI (Container Network Interface), use KubeProxy replacement, and set up Cilium Hubble for network observability. We will outline basic kubectl commands to evaluate the Cilium setup alongside network tests.
We assume you already have the basic project structurefrom part 1, as we will extend the configuration for Cilium. To follow along, check out the part 1 post.
I have been bootstrapping RKE2 and K3s clusters for a while now. I work on different platforms, both on-prem and in the cloud. This includes VMware, Proxmox, Nutanix, and almost every major cloud provider. This week, I have decided to take a different approach and discover something new! Bootstrap a Talos Kubernetes cluster on Proxmox using OpenTofu as the Infrastructure as Code (IaC) solution. My first interaction with Talos Linux was a couple of months back when Justin Garrison posted something about the ease of Kubernetes cluster deployment. I did not have much time back then, but here we come!
The blog post will be split into two parts. Part 1 will include a basic deployment of a Talos cluster using the out-of-the-box configuration, while Part 2 will contain the required configuration changes to use Cilium as our CNI. Get ready to roll up your sleeves and dive into the essentials of Talos Linux with OpenTofu on Proxmox.
