Skip to main content

Wrapping Up 2025

· 6 min read

2025 felt like a continuation of the momentum I built last year with Kairos—more code, more people, and more proof that collaboration beats any solo sprint. I spent the year balancing hands-on engineering with developer relations, and I kept learning that the best outcomes happen when we build with others, not just for them.

I’ll never forget this year, less for the work and more for my son’s birth. While I want to keep that personal, it’s too big to ignore. This new role as a parent is teaching me different ways to prioritize and work, and I’m so excited about it.

Update (2025-12-30): Added CNCF blog posts.

20 Years Working in Tech​

This year marked my 20th year in the tech industry. Over that time, I’ve worked on a lot of interesting projects and at some well-known tech companies. I earned a promotion to Staff Engineer at Spectro Cloud, and it feels like an important next step and a continuation of growth. It’s especially meaningful because I’m working on a project I find both interesting and impactful, alongside a team I truly admire, so I feel very proud of this accomplishment.

The Cloud Native OS​

That project is Kairos. It’s the most challenging tech I’ve worked on because it demands programming knowledge and a deep understanding of Linux and its components—init systems, boot mechanisms, and more. It’s a lot of fun for my inner nerd, but it spans so many areas that are still new to me. And as if that wasn’t challenging enough, a big portion of my work is also about promoting the project and improving the user experience. I’m learning that on the go; I only started doing DevRel work last year. Here’s what mattered most:

  • k0s integration: Kairos had first-class k3s support and a patchwork of community providers. I brought k0s in as a first-class option using the same Kairos-native cloud-init configuration, which means the same YAML-driven workflow, EdgeVPN-based P2P cluster formation, and a much smoother onboarding path. It turns Kairos into a Kubernetes meta-distribution, with native support for both k3s and k0s while keeping the immutable, secure-by-default experience intact.
  • Factory Web UI: To help people try Kairos and understand how the factory works, I made solid improvements to the Factory Web UI. That work led directly to my Pok8s talk on image-based systems and curated Kubernetes OS images, where I frame the problem space with playful metaphors and show why Kairos is a strong balance between convenience and control.
  • kairos-factory-action: Once the Factory Web UI makes the workflow tangible, the next step is to run it inside pipelines. I built the kairos-factory-action so teams can generate images quickly by passing a few arguments in GitHub Actions. It’s now what we use to test, build, and release Kairos.

My colleagues also shipped an amazing feature: a new Linux distribution specifically designed for image-based systems. On my side, I produced a Quick Start series for it. I’m proud of how it came out—it’s pushing me out of my comfort zone and giving me new ways to reach people and share Kairos, Hadron, and what I now see as the Cloud Native OS.

This year I delivered 11 presentations, mostly at CNCF-related events, and every stage was a chance to share what we’re building and listen to what users need. I’m also excited that 4 events are already scheduled for 2026 — see the full list on my public speaking page.

CNCF Blog Posts​

CNCF Groups and Meetups​

I continued co-hosting the CNCF Belgian Chapter and ran four well-attended meetups—around 30 people each—bringing companies and practitioners together. It’s been rewarding to see Belgium’s Cloud Native scene get stronger, and I’m excited to keep at it into 2026.

The CNCF removed working groups, which closed the Special-Purpose Operating System Work Group. I was bummed about not being a co-chair anymore, but it feels like a closing chapter. I’m now participating in the TAG Workloads Foundation, and I’m looking to reconnect with other OS makers to see if we can put something together.

Gratitude and Acknowledgments​

Like last year, thanks to my team for being so supportive and hardworking, you guys rock! To the many people in the Cloud Native space who have been present, you know who you are—thank you. And a very special thanks to William Rizzo. Together we worked on the k0s integration, delivered 4 of those talks, and he even presented at the very first CNCF Community meetup I organized this year. William is very knowledgeable about Kubernetes and CNCF, but most importantly I’m very happy to have made a friend along the way.

What I Missed (And Why That’s Okay)​

I didn’t hit everything I set out to do. I wanted deeper Kubernetes study (a homelab was supposed to help) and a content workflow that turns maintainer work into regular posts. I did level up my AI tooling, but the homelab is still on the backlog, and my content pipeline isn’t where I want it. That gap is a reminder to keep the goals a little out of reach so there’s room to grow.

Looking Ahead​

Heading into 2026, I’m very excited about the possibilities with Kairos and Hadron. Talking with our users and learning about the different projects where they’re using Kairos, I see all the things we’re doing well. Seeing what other projects are doing, I feel like we have a very stable foundation and more flexibility than most. So if the stars align, my goal is to keep promoting the project and introduce it as the Cloud Native OS.

To achieve that, I plan to make Hadron the default in Kairos docs while still keeping all other flavors as first-class options. I also want to publish at least one technical video each month in 2026.

I plan to submit a CNCF Ambassador application and aim for acceptance or clear feedback. I believe in Cloud Native technology, and part of that is helping people see how relevant the OS layer still is in the Kubernetes world.