Hacker GitHub

← All repos

kubernetes-retired/cluster-api-provider-nested

View on GitHub ↗ ★ 300 Go archived

Cluster API Provider for Nested Clusters

4 mentions on Hacker News by 3 people: 0 stories, 4 comments · first 2021-06-30 · latest 2024-07-18

Mentions per year 4 mentions · busiest year 2024 (2)
20082026
  1. Hard multi tenancy can't realistically be achieved in the same logical K8s cluster. And it is a moving target, which makes trying to secure it by admission controllers... not a great plan. One needs to look into things like VirtualClusters…
  2. > K8S done right is literally designed for multi tenancy No it is not. Not in the way they are using it. There are two main use-cases. One is multiple teams, in which case they are bound by their company's policies and guardrails The…
  3. Kubernetes has a lot of limitations from a multi tenancy perspective. It's functional, but I think it's not as polished as the rest of Kubernetes which is why Kubernetes has a multi tenancy SIG that spawned the hierarchical namespace…
  4. You 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-nest...