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.
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.
I love it when work and holidays come together! In this post, I am sharing my recent travel to California during February 2025 - a bit of an off-topic post for my usual content.
Another amazing Civo Navigate conference came to an end. In today's blog post, I wanted to share some highlights from the event. I had the chance to present Sveltos and how templating alongside Validate Health can be used to deploy and update different Kubernetes add-ons and applications effortlessly.
Below, I will dive into the key highlights from the conference, provide resources about tooling I found interesting and last but not least, provide more details about the Sveltos presentation!
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.
In Part 1 of the series, we demonstrated how to install Sveltos on a Kubernetes management cluster, deploy Kyverno and afterwards use the sveltosctl, the Sveltos Dashboard, alongside the Grafana Dashboard for observability. In today's post, we will take the next step and talk about the Dry-run feature, how to express a Sveltos ClusterProfile as a template and what the latest templateResourceRefs are.
It is already a year since I started getting more involved with ProjectSveltos. Over the past few months, a lot of work was put into making Sveltos not only more intuitive but also easier to use, all while preserving its core features and functionality.
This post will be split into two parts, with both sections covering the latest updates along with simple deployment examples to help you get started. So, let's dive into the world of Sveltos and explore what's new!
In a previous post, we described how to install multiple virtual clusters in a Civo cloud environment with vCluster.
Today's post is an update of the older deployment interacting with virtual clusters via a registered domain hosted in Cloudflare and using a LoadBalancer service to achieve that. Let's dive into it.
In a previous post, we described installing a Rancher server on an EKS cluster with Nginx Ingress, Let's Encrypt for TLS and Cloudflare for hosting a domain.
Today's post is an update of the old deployment which includes the latest Rancher stable Helm chart release and Proxy details hoping to fix cloud-init issues. We will provide an easy-to-follow guide outlining what's new, and why updating Rancher to a later version alongside caveats or issues faced during the deployment. For this demonstration, we will use a k3s cluster hosted on Civo Cloud.
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.