News for hackers. Stuff that matters.

Kubernetes is only a multi-node cluster kernel

Kubernetes is 'only' a multi-node cluster kernel. Some call it the Linux of the cloud.

And because K8s is only a kernel, there are now over 2000+ (open source) projects, all adding some extra functionality to it. Be it for observability, security, or networking. But all of these projects don't really collaborate and end-users don't ask for maturity of individual projects, they want sets/stacks of projects that integrate well.

Now every company has created some Stack with applications and configurations for Kubernetes, all trying to reinvent the wheel and spending an often shocking $ in doing so.

So here is my take:

- Let's create a new category in the Cloud Native Computing Foundation (CNCF) landscape and call it Integrated Stacks for K8s

- To be accepted, a stack needs to provide an open integration framework for other projects to add/integrate their apps

- Just like aLinux distro, each stack is ideal for some specific use case(s)

- A stack can be installed in one run, contains integrated apps that work out-of-the-box, has a (web) UI that acts as a desktop environment to provide easy and secure access to all features. Call it a new user experience for Kubernetes

Wouldn't it be great to have a list of all Kubernetes stacks available that everyone can use (and contribute to)? Just like (in the Linux analogy) you can choose between Linux Mint, Fedora, or Ubuntu.

We already created the first: https://github.com/redkubes/otomi-core

( 1 comment | on HN )
Re:Kubernetes is only a multi-node cluster kernel by yuppie_scum on Sunday July 10, 2022 @11:01AM (#32045380)
There are already a few major Helm repo aggregators (bitnami, etc) and applying and managing helm charts is fairly simple.

What you want can be achieved either with an Argo Flux repo or a Helmfile. Both of which are defined as code and easily versioned.

It would be nice for the industry to coalesce around a more common stack for sure.