k3v
multi-tenancy
Our great sponsors
| k3v | multi-tenancy | |
|---|---|---|
| 2 | 5 | |
| 684 | 952 | |
| - | - | |
| 0.0 | 0.0 | |
| over 4 years ago | 12 months ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
k3v
-
Kubernetes: Virtual Clusters As Development Environments
Alternatives: The concept of virtual clusters is rather new, so only few solutions for it exist. However, there are also open-source proof-of-concepts for a virtual cluster technology, such as k3v or the project from the Kubernetes multi-tenancy SIG.
-
vcluster - Open-Source Tool to Create Virtual Kubernetes Clusters // Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
Is this related at all to Rancher's (more or less abandoned) k3v project? https://github.com/ibuildthecloud/k3v
multi-tenancy
-
Kubernetes: Virtual Clusters As Development Environments
Alternatives: The concept of virtual clusters is rather new, so only few solutions for it exist. However, there are also open-source proof-of-concepts for a virtual cluster technology, such as k3v or the project from the Kubernetes multi-tenancy SIG.
-
create a configmap when a new namespace get created
This seems like a pretty good fit for HNC. You can restrict users to only create subnamespaces, and then ensure that the configmaps in the parent namespaces get propagated to the children.
-
Virtual Clusters For Kubernetes - Benefits & Use Cases
Virtual Kubernetes clusters are still a very new topic, but they are already available today. The multi-tenancy working group has presented an experimental solution in this area. k3v by Darren Shepherd is another proof of concept implementation in the open-source community.
-
Kubernetes Failure Stories
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...
-
Best Practice: Should each collection of resources be in their own namespace?
As a side note, hierarchical namespaces are coming, which makes things even more flexible: https://github.com/kubernetes-sigs/multi-tenancy/tree/master/incubator/hnc
What are some alternatives?
vcluster - vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
k3s - Lightweight Kubernetes [Moved to: https://github.com/k3s-io/k3s]
Kyverno - Kubernetes Native Policy Management
helmfile - Deploy Kubernetes Helm Charts
5-minute-production-app
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
synator - Synator Kubernetes Secret and ConfigMap synchronizer
minikube - Run Kubernetes locally
rancher - Complete container management platform
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle