News for hackers. Stuff that matters.

A comment on Show HN: Kardinal – Building light-weight Kubernetes dev ephemeral environments.

Re:Show HN: Kardinal – Building light-weight Kubernetes dev ... by shane_kerns on Friday August 23, 2024 @05:27AM (#41327478)
How is this different from vcluster? In fact vcluster has no dependency on Istio which I think is a huge detriment to kardinal. We use cilium so the istio requirement becomes a non starter for us.
[ Parent | on HN ]
Re:Show HN: Kardinal – Building light-weight Kubernetes dev ... by lostbean on Friday August 23, 2024 @08:15AM (#41328320)
It's a fair and valid comparison, and we're tracking this and other comparisons here: https://kardinal.dev/docs/references/comparisons

Regarding how Kardinal compares with vcluster, both aim to provide multitenancy within a single Kubernetes cluster, but they approach it differently.

vcluster is designed to offer a full Kubernetes experience to each tenant, including their own API server, control plane, and other Kubernetes-level components. This makes vcluster an excellent choice if you need strong isolation or want to test Kubernetes-specific features like custom CRDs or operators.

Kardinal, on the other hand, focuses on application-level multitenancy rather than providing the full Kubernetes stack to each tenant. This makes Kardinal lighter-weight and more efficient if you're primarily concerned with deploying and testing application-level changes.

[ Parent | on HN ]