hocus
vcluster
hocus | vcluster | |
---|---|---|
11 | 70 | |
3,122 | 5,597 | |
0.7% | 5.1% | |
8.9 | 9.8 | |
9 months ago | 5 days ago | |
TypeScript | Go | |
GNU General Public License v3.0 or later | 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.
hocus
-
We Replaced Firecracker with QEMU
I didn't want to go into all the technical details, but we have another write-up that goes into details about RAM management: https://github.com/hocus-dev/hocus/blob/main/rfd/0003-worksp...
Other than making sure we release unused memory to the host, we didn't customize QEMU that much. Although we do have a cool layered storage solution - basically a faster alternative to QCOW2 that's also VMM independent. It's called overlaybd, and was created and implemented in Alibaba. That will probably be another blog post. https://github.com/containerd/overlaybd
- Codespaces but open-source, client-only, and unopinionated
-
Google Cloud Workstations managed development environment is now GA
If you’d rather use a self-hosted alternative, we are building Hocus [0]. It’s still in alpha, but already supports prebuilds, VSCode, shared environment variables, and more.
[0] https://github.com/hocus-dev/hocus
-
[Self Hosted] Hocus - Alternative auto-hébergée à Gitpod et GitHub Codespaces, est maintenant publique sur GitHub
[https://github.com/hocus-dev/hocus
-
Hocus 0.2 Release: A Self-Hosted Alternative to Gitpod and GitHub Codespaces - Thank You for 2300+ Stars!
Check out our product launch post on Reddit here and the 0.2 release on GitHub here.
- Hocus 0.2 Released
- Show HN: Hocus – self-hosted alternative to GitHub Codespaces using Firecracker
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/)
What are some alternatives?
devpod - Codespaces but open-source, client-only and unopinionated: Works with any IDE and lets you use any cloud, kubernetes or just localhost docker.
capsule - Multi-tenancy and policy-based framework for Kubernetes.
swiss-chocolatey-lab - Create disposable dev environment VM's for GitHub repositories
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
devpod-react-server-comp
kiosk - kiosk 🏢 Multi-Tenancy Extension For Kubernetes - Secure Cluster Sharing & Self-Service Namespace Provisioning
devpod-react-server-components - Demo app of React Server Components.
cluster-api-provider-nested - Cluster API Provider for Nested Clusters
Vagrant - Vagrant is a tool for building and distributing development environments.
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
overlaybd - Overlaybd: a block based remote image format. The storage backend of containerd/accelerated-container-image.
k3s - Lightweight Kubernetes