Summary:

In part 1 of the series, we explored some of the recent vCluster Helm chart changes and how we can create the simplest vCluster possible. We also explored how we can assign specific Kubernetes worker nodes to vClusters based on taints, tolerations, and labels. Today, we will walk through the process of setting up Cilium L2 Announcements to make the vCluster available via a LoadBalancer service and then deploy and use the vCluster Platform.

Summary:

It has been a while since my last post on vCluster. After working more closely with the tool, I decided to update the series and show you what changes when it comes to a local setup.

Summary:

To make our lives easier when it comes to manual Sveltos progressive rollout approvals, we will use Botkube and Slack.

Summary:

In a previous post, we looked at using MkDocs and MkDocs Material with the Mike plugin for versioning. This helps in creating a static site on GitHub with GitHub workflows. As MkDocs Material entered maintenance mode on the 6th of November 2025, I decided to migrate to Zensical.

Summary:

KubeCon Amsterdam 2026 highlights.

Summary:

Cloud Native Rejekts Amsterdam 2026 highlights.

Summary:

From one lake to another. From Lake Plastira to Kastoria and Prespes. If you are a nature lover and have a few more days in Greece, I would recommend visiting them.

Summary:

No work travel this time. Only a few days to recharge my batteries in a quiet, yet magnificent place in Greece, Lake Plastira. If you happen to be there at the end of February or the beginning of March, check out the blog for quick and easy hikes and walks.

Summary:

Taking a step further from where we left off in part 1 of the series. We will look at an example that mixes Sveltos rollouts with progressive rollouts, validation, and checks after validation. This gives us tailored control over deployments and updates.

Summary:

Rollouts and progressive rollouts are essential for operation teams and developers. They help deploy new features and updates safely and with less risk. Today, we will explore how Sveltos' Rollout and Progressive Rollout features enable platform teams and engineers to update confidently, without fear! 💪

Summary:

Learn how to use Sveltos to automate the creation of Cluster API (CAPI) clusters on Proxmox using the CAPMOX provider.

Summary:

We continue where we left off with the CAPMOX deployment. In this post, we will go through common issues during deployment and the tools used to troubleshoot and resolve them.

Summary:

Learn how to use the image-builder to craft a base Ubuntu 24.04 image for Kubernetes and how Cluster API (CAPI) helps teams provision, manage, and automate the lifecycle of Kubernetes clusters on a Proxmox server.

Summary:

Taking the latest updates introduced in part 4, we will add Ceph using Rook for file and block storage suitable for the different applications running in Kubernetes.

Summary:

We continue where we left off in part 4. We add Longhorn persistence block storage to the Talos Linux cluster

Summary:

My KCD Geneva 2025 highlights.

Summary:

Talos Linux Kubernetes module updates for ongoing operations.

Summary:

An easy way to migrate ArgoCD running on an RKE2 cluster from Ingress NGINX to Cilium Ingress.

Summary:

This is part 3 of the step-by-step guide to creating Kubernetes managed clusters on Azure Cloud using Cluster API (CAPI) and Sveltos! We will give platform teams and seasonal engineers a simple, secure, and flexible way to build Kubernetes clusters.

Summary:

This is a quick summary of updating Docusaurus from v3.8 to v3.9 and what the required modifications/steps are.