Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’ve tried minikube, microk8s, the one bundled with Docker Desktop for Windows, k3s and Red Hat CodeReady. Of these I had the best experience with Kind (by far) and the worst experience with CodeReady (also by far).

The thing I like most with Kind: Being inside Docker makes Kind very ephemeral. Every time I start it up I get a fresh cluster. I know where everything is and it doesn’t contaminate my machine.

Since some of the authors are on the thread I would like say thank you. I really appreciated the recent improvements to kubectl-integration and the addition of local storage.

In the future I would like it to be easier to play with pod and network policies, reduced cluster startup time and reduced node image sizes.

Keep up the good work!



Out of curiousity, as I'm thinking of looking at CodeReady for openshift, what problems did you have there?


OP is right about CodeReady - I’ll unhesitatingly say it’s a pos. It’s way too heavyweight for even a high end laptop. It’s single node only. It’s falls over if you enable monitoring unless you can give it 8 cores and 12GB, then it sort of works but is too slow. The 3 times I tried deploying the provided samples - they didn’t work out of box. It also requires you to download new release every month I think - no in place updates I think.


It used too many resources for my computer. It took about 10 minutes to start a cluster and once the cluster was up and running my computer had a hard time performing any additional tasks - like having IDE open and compiling source code.

In comparison k3s takes seconds to start a cluster. Kind takes about a minute. Neither will consume resources to a point where my computer becomes unusable.

I reported my experience to Red Hat and they replied that it was to be expected.

EDIT: Found the issue https://github.com/code-ready/crc/issues/617.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: