Docusaurus: Update from 3.4.0 to 3.7.0
Docusaurus: Update from v3.4.0 to v3.7.0. Tips and Tricks.
The year the post went online
View All TagsDocusaurus: Update from v3.4.0 to v3.7.0. Tips and Tricks.
Welcome to part 4 of the dual-stack
series! In parts 1, 2, and 3, we walked through how to set up dual-stack
networking on a Proxmox server using our Internet Provider. We also showed you how to deploy RKE2 Kubernetes clusters and share both IPv4 and IPv6 services across them. Now, in the final part of the series, we are diving into some of the most commonly used features of Cilium for a home lab setup! Let’s get started!
Are you ready to simplify how your Platform team spins up and down development environments while improving DevX? In this post, we demonstrate how CAPI, Sveltos, and Cyclops work together to automatically create Kubernetes environments while allowing developers to interact and manage their applications in a user-friendly environment. It is not magic, it is the power of Sveltos combined with the right tooling!
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!
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.