Hacker News Reader

Comment by pestaa | Hacker News Reader

I want to get into OpenShift/OKD, but the distributed storage systems are quite frightening. There are plenty nightmare stories related to GlusterFS performance.

However, strange as it sounds, I'm looking to deploy a cluster on a single node, primarily for the Kubernetes API & ecosystem (so many tooling options).

What is your opinion on running K8s this way, and having only local RAID storage?

View on HN

As mentioned, CodeReady Containers (CRC) is the easy button for a single node setup [0]. But it is heavy for a single node. Alternatives for labs and demos are learn.openshift.com [1] and the All-in-One VM blog [2]. Storage isn't too important in a single node setup unless you're looking for Metrics, Logging, and Monitoring to be turned on. You could use NFS if you have to. Just don't do that in Production, IMO.

[0] https://developers.redhat.com/blog/2019/09/05/red-hat-opensh...

[1] https://learn.openshift.com/

[2] https://www.openshift.com/blog/revamped-openshift-all-in-one...

This sounds like you want https://k3s.io, a kubernetes distribution specially made for single node and probably much simpler.

I have tried running OKD/OpenShift locally - even using the latest retake on it - Code Ready Containers. It is way too resource intensive for a single VM. That is before you start the prometheus/monitoring/alerting stuff or metrics server - at that point your single VM is good as dead.

You can just learn plain old K8S - get an Ubuntu VM and snap install microk8s. Add another vm as a node and it works well for most part and sans storage stuff (you can do NFS though) you can learn almost everything. After that catching up to OpenShift specifics is not that big of a deal - it's not all that different.

Reply on news.ycombinator.com