Hello world!
I want to release to internet my custom immutable rolling-release extreme-simple Linux distribution for Kubernetes deployments.
I was using this distribution for about the last 6 years on production environments (currently used by a few startups and two country's public services). I really think that it could be stable enough to be public published to internet before 2024.
I'm asking for advice before the public release, as licensing, community building, etc.
A few specs about the distribution:
-
Rolling release. Just one file (currently less than ~40Mb) that can be bootable from BIOS or UEFI (+secure boot) environments. You can replace this file by the next release or use the included toolkit to upgrade the distribution (reboot/kexec it). Mostly automated distribution releases by each third-party releases (Linux, Systemd, Containerd, KubeAdm, etc).
-
HTTP setup. The initial setup could be configured with a YAML file written anywhere in a FAT32 partition or through a local website installer. You can install the distribution or configure KubeAdm (control-plane & worker) from the terminal or the local website.
-
Simple, KISS. Everything must be simple for the user, this must be the most important aspect for the distribution. Just upstream software to run a production ready Kubernetes cluster.
-
No money-driven. This distribution must be public, and it must allow to be forked at any time by anyone.
A bit of background:
I was using CoreOS before Redhat bought them. I like the immutable distro and A/B release aspect of the CoreOS distribution. After the Redhat acquisition, the CoreOS distribution was over-bloated. I switched to use my own distribution, built with Buildroot. A few years later, I setup the most basic framework to create a Kubernetes cluster without any headache. It's mostly automated (bots checking for new third-party releases as Linux, Systemd, Containerd, KubeAdm, etc; building, testing & signing each release). I already know that building a distribution is too expensive, because of that I programmed few bots that made this job for me. Now days, I only improve the toolkits, and approve the Git requests from thats bots.
Thank you for your time!
The first improvement (Media Foundation by FFMPEG) could be significant. Currently, VALVe generates large shaders to re-render those Media Foundation videos into other free codecs. These shaders can be several gigabytes in size for some games with lengthy videos. With FFMPEG, those videos could be played without being re-encoded as shaders.