Re:Kubernetes Failure Stories
by bcrosby95 on Thursday February 11, 2021 @03:59PM
(#26107068)
A Kubernetes for Kubernetes! But what about when we want to upgrade that?
[ Parent
| on HN ]
Re:Kubernetes Failure Stories
by dabeeeenster on Thursday February 11, 2021 @04:28PM
(#26107519)
I mean thats simply Kubernetes for Kubernetes for Kubernetes. Lets go!
Re:Kubernetes Failure Stories
by testplzignore on Thursday February 11, 2021 @04:38PM
(#26107662)
I need a Kubernetes Kubernetes Kubernetes Kubernetes Kubernetes emulator so I can run Civilization 14 on my iPhone 35XSXS.
Re:Kubernetes Failure Stories
by higeorge13 on Thursday February 11, 2021 @04:57PM
(#26107923)
Inception!
In a way this reminds me of Kubernetes Virtual Clusters. Each virtual cluster has its own tenant control plane, namespaces. Multiple virtual clusters exist in a super cluster.
https://github.com/kubernetes-sigs/multi-tenancy/tree/master...
I think at a certain point up in the stack you don't want to have another orchestrator for the orchestrator. You would just tell each team to keep their cluster up-to-date without creating a (dangerous) master button to update them all at once.
Wake me up when I can finally run a bare-metal Kubernetes cluster in Kubernetes to get rid of all my hardware.