[>] Introducing KRaftCloud
Wait, what? What am I talking about?
I gave a talk about KRaft at the local Developer's Conference in July. It was a packed session and I had a ton of meaningful conversations with people after it was done. The reception of this project, as well as the feedback, has made me think about the next step for this project.
Features and Changes
>
KRaft has progressed in ways I didn't quite expect, and has a lot more potential in Mauritius. The project started out as an easy way to run workshops and labs on Kubernetes without the expensive cloud bills, which I think it has successfully achieved. However, personally, I have been more and more involved with digital sovereignty in Mauritius and filling gaps in our cloud offerings which the other local cloud companies do not cover for. I see potential for KRaft to be a lot more than
just a workshop platform.
This brings me to my idea about KRaftCloud.
KRaft has been built with independence in mind, which means that there is no vendor lock-in or requirements on the software or hardware stack you run underneath. This has worked amazingly, and you can bring everything of your own, including ingressclass, storageclass, host K8s distro, and more. However, putting effort into the interoperability comes at the cost of increased friction and effort being spent there which could be better used elsewhere.
The idea behind KRaftCloud is to turn kraftcloud.dev into an "upstream" version which I will gradually become a real cloud provider running from my homelab (if I can even call it a lab at this point). I will have the benefit of shedding some of the interoperability weight, which will let me add all the features I have been wanting to add, without worrying about going against the principles behind KRaft (no lock-in, lightweight, simple).
All of that means I have a lot of work ahead of me. I will start by creating a Forgejo server to host everything relating to KRaft, as well as the core KRaft project, which should be available somethime soon on
git.kraftcloud.dev. Features I am looking forward to include S3, DNS, Mail, potentially VPS's, static sites, maybe cloud functions, managed databases (particularly postgres), and scale-to-zero hosting.
Exciting times ahead!
