3 ms·
I've had the same experience, absolutely love Microk8s, though I am hopeful about k3s and k3d (k3s in Docker). As of right now they "mostly" work, but unfortuna
by gavinray 7y ago
I've had the same experience, absolutely love Microk8s, though I am hopeful about k3s and k3d (k3s in Docker). As of right now they "mostly" work, but unfortunately that's enough to break things.
Also, you can't beat the one-line snap install for Microk8s.
- sandGorgon 7y agoCould you talk about what breaks in k3s/k3d ? We have been considering having a desktop -> production cluster on k3s.
- e12e 7y agoOne caveat on my previous comment - if you use any one of these in production (I guess k3s is the most likely one there) - then I think using it for dev should be fine. The biggest issue is differences between versions - we're deploying to managed k8s in azure, and need a dev environment that works similarly.
- sandGorgon 7y agoHmm..do you mean that k3s does not track the cloud deployments closely ? So the dev -> production experience is less than ideal ? We are planning to use k3s for local development and deploy to EKS...so this is interesting.
- e12e 7y agoYes, that's been my experience so far - trying things (now) on microk8s and managed azure k8s. The main thing is that documentation for microk8s and the design seems aimed at "behave as/pretend to be a real k8s" - including things like ingress.
- gavinray 7y agoI just tried to set up the same stack of ~7 services I had running on Microk8s locally, and a few things went wrong in the process. Couldn't get it running. My kubectl-fu is not strong enough to fix it, so for me that was a dealbreaker. Though I am super passionate about k3s and support the hell out of everything Rancher Labs does, so by no means did it leave a bad taste in my mouth.