3 ms·
One 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
by e12e 7y ago
One 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.