6 posts tagged with "Proxmox"

Introduction​

Welcome to part 3 of the dual-stack series! In part 1 and part 2, we discovered how to enable dual-stack on a Proxmox server using our Internet Provider and deploy RKE2 clusters. In today's post, we continue our journey and enable a Cilium Cluster Mesh between two RKE2 clusters. The goal is to share IPv4 and IPv6 services between the different clusters effortlessly. Let’s dive in!

Introduction​

Welcome to part 2 of the dual-stack series! In part 1, we covered how to enable IPv6 Prefix allocation using pfsense on Proxmox with Fritz!Box as a home router. The setup allows virtual machines in a dedicated interface to receive an IPv4 and an IPv6 address. If you have completed part 1, you can continue with the dual-stack RKE2 setup powered by Cilium.

Introduction​

Welcome to the first post in the dual-stack deployments series! In part 1 of the series will set the stage for everything to come. Dual-stack is when a machine can talk both IPv4 and IPv6. Part 1 aims to guide users through enabling and configuring IPv6 Prefix allocation for virtual machines in a Proxmox environment, using pfsense. The setup will be used later on for Kubernetes Deployments, Service Mesh and Global Service Sharing powered by Cilium.

Introduction​

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.

Introduction​

Welcome to part 2 of the Talos Linux Kubernetes cluster bootstrap on the Proxmox series. Today, we will take the next step with our configuration and go through the process of enabling Cilium as our CNI (Container Network Interface) with KubeProxy replacement enabled and 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 structure from part 1 as we will extend the configuration for Cilium. To follow along, check out the part 1 post.

Introduction​

It's been a while now since I am bootstrapping RKE2 and K3s clusters on different platforms, on-prem and in the cloud, including VMware, Proxmox, Nutanix and pretty much every well-known 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-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.