4 ms·
"You know what? We need more layers. On top of this." Heh. Service Mesh!
by tyingq 5y ago
"You know what? We need more layers. On top of this."
Heh. Service Mesh!
- rantwasp 5y agoK8s on K8s! K64s!
- voidfunc 5y agoBut can it run on an N64?
- rantwasp 5y agoit starts at Nintendo 69.
- yongjik 5y agoKuberneteuberneteuberneteuberneteuberneteuberneteuberneteubernetes is a perfect name for the beautiful system you are about to architect: it's an ancient Greek word for helmsman-man-man-man-man-man-man-man, who is in charge of helmsman-man-man-man-man-man-man, who is in charge of ... (...sorry =_=)
- verst 5y agoYou joke, but have you looked at K8s VirtualCluster? Separate control planes for each tenant within a K8s cluster. https://github.com/kubernetes-sigs/cluster-api-provider-nested/tree/main/virtualcluster https://github.com/kubernetes-sigs/cluster-api-provider-nest...
- rantwasp 5y agoof course. of course! it’s k8s clusters all the way down
- lubujackson 5y ago"Nobody will ever need more than K64." - Robo-Gates
- ArchOversight 5y agoMay I introduce you to https://gardener.cloud https://gardener.cloud?
- goodoldneon 5y agoA service mesh isn't a layer on top of K8s, but rather fills gaps in K8s feature set. Service meshes are great for managing traffic between services: authentication, authorization, encryption, traffic shaping, etc.