Kubernetes for personal projects? No thanks
Oh man, the original article went way over the author&#x27;s head. The point of the original article was that even though Kubernetes is <i>primarily</i> useful for tackling the challenges involved with running many workloads at enterprise scale, it <i>can</i> also be used to run small hobbyist workloads at a price point acceptable for hobbyist projects.<p>Does that mean that Kubernetes should now be used for <i>all</i> hobbyist projects? No. If I&#x27;m thinking of playing around with a Raspberry Pi or other SBC, do I need to install Kubernetes on the SBC first? If I&#x27;m thinking of playing around with IoT or serverless, should I dump AWS- or GCE-proprietary tools because nobody will ever run anything that that can&#x27;t run on Kubernetes ever again? If I&#x27;m going to play around with React or React Native, should I write up a backend just so I can have something that I can run in a Kubernetes cluster, because all hobbyist projects must run Kubernetes now, because it&#x27;s cheap enough for hobbyist projects? If I&#x27;m going to play around with machine learning at home, buy a machine with a heavy GPU, figure out how to get Kubernetes to schedule my machine learning workload correctly instead of just running it directly on that machine, because uhhh maybe someday I&#x27;ll have three such machines with powerful GPUs plus other home servers for all my other hobbyist projects?<p>No, no, no, no, no. Clearly.<p>But maybe I envision my side project turning into full-time startup some day. Maybe I see all the news about Kubernetes and think it would be cool to be more familiar with it. Nah, probably too expensive. Oh wait, I can get something running for $5? Hey, that&#x27;s pretty neat!<p>Different people will use different solutions for different project requirements.