Ah, this raises an interesting discussion I've been wanting to have for a while.
There are potentially lots of things you could call a distro.
Most linux distro's are made up of several layers:1. boot loader - components to get the kernel running
2. kernel - provides a place to run higher level software
3. os level services - singletons needed to really call the os an os. (dhcp, systemd, dbus, etc)
4. prebuilt/tested, generic software/services - workload (mysql, apache, firefox, gnome, etc)
For sake of discussion, lets map these layers a bit, and assume that the openshift specific components can be added to a vanilla kubernetes. We then have
1. linux distro (could be k8s specific and micro)
2. kubernetes control plane & kubelets3. openshift components (auth, ingress, cicd/etc)4. ? (operators + containers, helm + containers, etc)
openshift use to be defined as being 1-3.
As things like ake/eks/gke make it easy to deploy 1-2, maybe openshift should really become modular so it focuses more on 3 and 4.
As for having something that provides a #1 that is super tiny/easy to maintain so that you can do #2 on top easily, I'm for that as well, but should be decoupled from 3-4 I think. Should you be able to switch out your #1 for someone elses #1 while keeping the rest? That's the question from previous in the thread.
#4 I think is very important and while the operator framework is starting to make some inroads on it, there is still a lot of work to do to make an equivalent of the 'redhat' distro of software that runs on k8s.
A lot of focus has been on making a distro out of k8s. but its really mostly been at the level of, how do I get a kernel booted/upgraded. I think the more important distro thing #4 is how do you make a distribution of prebuilt, easy to install software to run on top of k8s. Redhat's distro is really 99% userspace and a bit of getting the thing booted.
Its value is in having a suite of prebuilt, tested, stable, and easily installable/upgradable software with a team of humans that can provide support for it. The kernel/bootloader part is really just a means to enable #4. No one installs a kernel/os just to get a kernel. This part is currently lacking. Where is the equivalent of Redhat/Centos/Fedora for #4.
In the context of OKD, which of these layers is OKD focused on?