vcluster
zarf
Our great sponsors
vcluster | zarf | |
---|---|---|
70 | 6 | |
5,577 | 1,165 | |
12.0% | 22.3% | |
9.7 | 9.5 | |
about 13 hours ago | 5 days 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.
vcluster
-
Amazon EC2 Enhances Defense in Depth with Default IMDSv2
Kubernetes? You mean the container orchestration system where they forgot to add Multi-tenancy? And no namespaces are not Multi-tenancy...
https://www.vcluster.com/
-
Mirantis Unveils K0smotron: An Open-Source Kubernetes Management Project
Whats the difference between this and vcluster (https://github.com/loft-sh/vcluster)?
-
Codespaces but open-source, client-only, and unopinionated
Yep, as we see it they compliment each other quite well. DevPod takes your workspace to the cloud and DevSpace let's you develop against your Kubernetes cluster - potentially the same one you used to start your workspace.
Internally we use both in our development setup, spinning up remote workspaces using DevPod, installing DevSpace and kind into the devcontainer, then using DevSpace to develop against the cluster. See the vcluster setup[1] as an example
[1]https://github.com/loft-sh/vcluster/tree/main/.devcontainer
-
Anyone using Kata Containers?
The tenants are internal dev teams so yeah maybe not. I was considering multi-tenanting different environments isolated at the kube layer with vCluster and have the vCluster pods running in Kata containers giving maximum isolation but still having a single management cluster. Ideally also avoiding the need to buy a second set of hardware for a dev environment
-
Multi-tenancy in Kubernetes
Vcluster
-
Kub'rin' a breeze: Developing on ephemeral cloud-based K8s clusters
Looks interesting. How does this solution compare to vcluster?
-
Same cluster for different development environments
sounds like the best option for you , is a tool called VCluster by loft ( https://www.vcluster.com/) , this way you can install as many k8s cluster as you want in the same k8s host cluster , those cluster share workers nodes and networking, but each has a separated "api server" , so it looks like you have a dedicated cluster with their own namespaces and tools . take a look at the docs to get a better understanding and how they work.
-
Is it a good idea to use k8s namespace-based multitenancy for delivering managed service of an application?
We're about to run a PoC with vcluster for isolated sandboxes, this might be relevant to you too
-
Questions for Heroku-like Project
I think namespaces, RBAC and network policies are sufficient to partition users from the same organisation. I would investigate the use of vcluster ig you want to give your users even more isolation and capability (such as installing CRDs)
-
Multiple Tenancy, Namespaces, Securing Workloads
Depends on the use case. Namespaces provides soft isolation (so it means they share same Apiserver, PV's and global resources such as CRD's), but can be restricted with network policies. So it means, there's still potential in breaking other namespaces if you change PV's or CRD's which are used by other namespaces. Multi-Cluster solution can provide full isolation, but its also really expensive in resource consumption and maintenance/management effort. If namespaced-isolation isnt enough for your use case, you can consider vclusters (https://www.vcluster.com/)
zarf
- Zarf: K8s in Airgapped Environments
-
Air gapped on prem install - what would you do?
There is a tool written for this exact scenario! (disclaimer: I am a maintainer) https://github.com/defenseunicorns/zarf . Zarf can create packages out of all of your images, Helm charts, manifests... and deploy that package w/ zero dependencies on the other side (you can even use k3s built into the default init package if you don't have a cluster). The docs do it more justice https://docs.zarf.dev/docs/zarf-overview .
- Zarf – DevSecOps for Air Gap and Limited-Connection Systems
- GitHub - defenseunicorns/zarf: K8s Airgap Buddy
- zarf: K8s Airgap Buddy - Zarf massively simplifies the setup & administration of kubernetes clusters "across the air gap". It provides a static go binary CLI that can pull, package, and install all the things your clusters need to run. It caches downloads (for speed), hashes packages (for security)
-
What is the Hardest Environment to Deploy to?
We're working on https://github.com/defenseunicorns/zarf which can deploy to bare metal and an airgap environment
What are some alternatives?
capsule - Multi-tenancy and policy-based framework for Kubernetes.
helmify - Creates Helm chart from Kubernetes yaml
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
kiosk - kiosk 🏢 Multi-Tenancy Extension For Kubernetes - Secure Cluster Sharing & Self-Service Namespace Provisioning
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
cluster-api-provider-nested - Cluster API Provider for Nested Clusters
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
sbom-operator - Catalogue all images of a Kubernetes cluster to multiple targets with Syft
k3s - Lightweight Kubernetes
hauler - Airgap Swiss Army Knife