k3s
multi-tenancy
k3s | multi-tenancy | |
---|---|---|
7 | 5 | |
15,937 | 952 | |
- | - | |
9.2 | 0.0 | |
about 3 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.
k3s
-
Kubernetes: Multi-cluster communication with Flomesh Service Mesh (Part 2)
In this demo, we will be using k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker, to create 4 separate clusters named control-plane, cluster-1, cluster-2, and cluster-3 respectively.
-
Pipy: Protecting Kubernetes Apps from SQL Injection & XSS Attacks
To run the demo locally, we recommend k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.
-
When a node goes down, how long should k8s wait before migrating pods to other nodes?
I've been messing around with k8s (k3s) lately, and got to the "issue" of downtime/inconsistencies caused by one of multiple workers being down, who had pods running on them. I found a couple useful parameters here that helped me reduce the time needed to redeploy the old pods on other nodes, as well as stop sending requests to the NotReady node. But that got me thinking, how long should k8s wait before doing these things? Or is there perhaps a better option for increasing avaliability?
-
Kubernetes Development Environments – A Comparison
Local Kubernetes clusters are clusters that are running on the individual computer of the developer. There are many tools that provide such an environment, such as Minikube, microk8s, k3s, or kind. While they are not all the same, their use as a development environment is quite comparable.
-
Local Cluster vs. Remote Cluster for Kubernetes-Based Development
Since the developer is the only one who has to access this cluster for development, local clusters can be a feasible solution for this purpose. Over time, several solutions have emerged that are particularly made for running Kubernetes in local environments. The most important ones are Kubernetes in Docker (kind), MicroK8s, minikube and k3s. For a comparison of these local Kubernetes options, you can look at this post.
-
Kubernetes: Virtual Clusters As Development Environments
With local Kubernetes environments such as minikube or k3s, developers can create their own Kubernetes clusters on their local computers. This often leads to developers struggling with the management and setup of these pared-down Kubernetes technologies that are also not completely realistic compared to “real-world”, cloud-based environments. The upside of this approach is that the developers have full control over their environment and can independently create it whenever they need it.
-
[Recap] The API Hangout #31
K3d - a lightweight wrapper to run k3s in docker.
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?
minikube - Run Kubernetes locally
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
devspace-plugin-loft - Loft Plugin for DevSpace - adds commands like `devspace create space` or `devspace create vcluster` to DevSpace
Kyverno - Kubernetes Native Policy Management
cilium - eBPF-based Networking, Security, and Observability
helmfile - Deploy Kubernetes Helm Charts
kubefwd - Bulk port forwarding Kubernetes services for local development.
5-minute-production-app
fsm - Lightweight service mesh for Kubernetes East-West and North-South traffic management, uses ebpf for layer4 and pipy proxy for layer7 traffic management, support multi cluster network.
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
k3v - Virtual Kubernetes
synator - Synator Kubernetes Secret and ConfigMap synchronizer