Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

Hi, I'm around today if you'd like to talk about virtual Kubernetes clusters or have questions about my talk, "Virtual clusters for Kubernetes: use cases." Things might be async at times as I have some meetings but I'm happy to chat :slightly_smiling_face: <https://youtu.be/_1_iTue9GZU>

<@U03JTU6RHPV> - I just wanted to say that I love the vcluster project. Sadly we have not integrated it into our workflows yet but a few months ago a gave it a little spin during the Digital Ocean K8s Challenge and it was awesome to see how much can be achieved with this piece of software in a short period of time: <https://github.com/danielhass/digitalocean-k8s-challenge>

Shout out to you and Loft Labs for building and maintaining it.

<@U03JX7XTL9G> Thanks so much, I will pass that on to the team. We're so happy that people are finding vcluster so useful. Let me know if you ever want to talk through how to use it or anything.

I can't take credit for building it, we have super smart engineers :slightly_smiling_face:

<@U03JTU6RHPV> this was a great talk, thanks for recording it! I'm definitely going to give `vcluster` a shot.

<@U03710Z0USD> Thanks a lot :slightly_smiling_face: I"m glad you enjoyed it. Have fun with vcluster and feel free to let me know if you have any feedback or questions.

<@U03JTU6RHPV>
A lil late, but what are some use cases where `vcluster` is preferred over `kind` ?

I saw the talk and thought that `kind` also fulfils the highlighted use cases
• A differentiating one could be for multi-tenancy prod environments, are there others that I'm missing?

I don't think so. I think vcluster is still faster than kind. Like with kind I think you need to pull images again for each cluster. I haven't done a comparison with metrics or anything. kind is great.