if you can do this (and build a great experience around it), you have a winner.
k3d.io does it somewhat...but not all the way. Updates,rollbacks, etc - everything that a sysadmin need.
if you can do this (and build a great experience around it), you have a winner.
k3d.io does it somewhat...but not all the way. Updates,rollbacks, etc - everything that a sysadmin need.
Here is a demo video: https://asciinema.org/a/V1UFSxz6JHb3rdHpGrnjefFIt?speed=1.75
Having said this, K8s is very complex and while its most common functionality works inside the container, we've not yet tested it all.
Here is a doc that describes this in more detail, including what is supported and not supported at this time: https://github.com/nestybox/sysbox/blob/master/docs/user-gui...
You can find kindbox here if you are curious: https://github.com/nestybox/kindbox
Having said that, we have certain limitations at the moment (e.g. we don't run all cni's), but we are not relying on priv containers as i believe is the case for existing K8s-in-docker solutions (pls correct me if i'm wrong in k3d's case).
Btw, we haven't tested k3d.io & sysbox interaction yet (part of our roadmap), but i believe we should be able to interoperate after making some minor adjustments. That would allow existing k3d users to operate in a more secure environment.
> if you can do this (and build a great experience around it), you have a winner.
Genuine question. I'm not that familiar with Kubernetes. Can you explain the pain this solves? What is this winning at?