vcluster VS jspolicy

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/

Whats the difference between this and vcluster (https://github.com/loft-sh/vcluster)?

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

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

Vcluster

Looks interesting. How does this solution compare to vcluster?

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.

We're about to run a PoC with vcluster for isolated sandboxes, this might be relevant to you too

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)

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/)

I struggled with understanding OPA too! I have not seen this mentioned, but one straightforward alternative is JSPolicy (https://www.jspolicy.com/), which allows you to write policies in Javascript or Typescript. It is really easy to understand and get started.

You will likely want to implement certain restrictions, limits, quotas, or security policies for your Kubernetes clusters. This could help with auditing or monitoring tasks, or with standardizing a quota for certain resources. Tools like the Open Policy Agent (OPA), jsPolicy, or Kyverno can be used based on your needs. Many developers are more comfortable with YAML or JavaScript, so Kyverno or jsPolicy might be preferred.

In 2021 we also released two new open source projects: vcluster, a tool for creating and using virtual Kubernetes clusters, and jsPolicy, a tool for writing policies for Kubernetes clusters in JavaScript or TypeScript. vcluster especially gained a lot of traction and our CEO Lukas Gentele gave a talk about it at KubeCon Los Angeles.

Either engine could be a good choice for your business. Consider which factors are most relevant to your project and your use case before you make a decision. You can learn more about jsPolicy here and about OPA here.

Loft Labs is the creator of several popular open-source projects in the cloud-native technology space, including the Kubernetes developer tool DevSpace, the certified Kubernetes distribution vcluster, and the policy engine jsPolicy. The company’s commercial product, Loft, enables any organization to scale self-service access to Kubernetes to hundreds or even thousands of engineers. Loft's customers span from fast-growing startups Gusto, Urbint, and HqO to well-established Fortune 500 companies that include one of the largest U.S. financial institutions and one of the world’s largest car manufacturers.

Loft Labs also recently released vcluster, a first-of-its-kind virtual cluster technology for Kubernetes. jsPolicy now available at www.jspolicy.com and on Github.

Would you mind explaining why is it hard for admission controllers to check container definitions of the pod? I've never used OPA or Kyverno, but I want to start contributing to a competitor project, so I am really curious to find out. Thank you! :)

This makes sense and I made the assumption that someone thought about the root-ability thing after I saw loft-sh/jspolicy.