andrewrynhard

With Kubernetes you can schedule workloads in a number of different ways. Let’s say you insisted on having a shell and package manager. Run your favorite distro’s container as a DaemonSet. With the proper mounts and permissions you can do a lot. In other words use Kubernetes to do the things need to do. Then what role does the OS really play? Well in the case of Talos it’s only there to run Kubernetes.

In machined (PID1 of Talos).

In the case of Talos, Kubernetes can provide the flexibility you want from a more traditional Linux distribution.

Have you tried our Slack fir support?

This is correct. You could have a privileged pod that mounts up the host and you can do things from there but even then the OS is read only.

Oh I am well aware of RH CoreOS.

I would say that CoreOS is gone because RH destroyed it. Not because people didn't use it.

We mention CAPI but certainly not 2.0 since the CAPI we are referring to is "Cluster API" and they only have 1.0.

For folks who are all in on a single cloud provider it might not make sense, but if you run Kubernetes in multiple clouds, on-premise, edge, etc. then it starts to make a lot of sense since you get consistency.

The same spirit as CoreOS but it is something entirely different. Written from PID1 up solely for the purposes of running Kubernetes.

It is a 50MB squashfs.

Have you guys taken a look at Talos?