Kubernetes platforms face the same challenge Linux solved decades ago: how to let users install only what they need and build community-driven package ecosystems.
In Cozystack, we built an APT-like package system on FluxCD and OCI artifacts. The operator introduces Package and PackageSource CRDs - analogous to dpkg and sources.list - with pluggable repositories, dependency resolution, and content-based versioning.
They say it all began rather dully.
First, artificial intelligence learned to write code. Then it learned to write it better than most people. And then a thing came to light that the industry had somehow overlooked for decades: the most expensive resource in open source isn’t development. Not review. Not even the CI devouring data-center budgets. The most expensive thing turned out to be the one there were never enough people for.
An easy and visual explanation that demonstrates what happens when you create a new pod in Kubernetes. It shows how the apiserver, scheduler, controller-manager, and kubelet work together, operating on the same Kubernetes resource. @kcdczechslovak5840
#347: Andrei Kvapil has been around Kubernetes since the early days. Contributor to Cilium, Kubevirt, and a handful of other projects you probably use without realizing it. He is also the maintainer of Cozystack, a CNCF sandbox project, and the CEO of Aenix, the company behind it.
In our previous article, we showed you how to build a platform that deploys multiple managed applications through a unified API and UI…
I have spent many years dreaming about building my own cloud platform. After several attempts within different companies, I finally launched my own project, Cozystack. In this article, I am going to share our experience and our approach to building a modern infrastructure platform around Kubernetes and its API. I’ll dive into the “platform approach” — what platform is, how it works, who it’s for, and how to get one off the ground. Plus, I’ll compare different architectures, explain why we went with K8s, and show you how we put together a production-grade solution based on it.
When it comes to running virtual machines in Kubernetes via KubeVirt, the first question engineers ask is: “What is the overhead?” Let’s dive into the details and break it down by three key areas: compute, storage, and network.
To get why there’s almost no CPU overhead, we need to look at how the Linux kernel handles containers.
