3 ms·
This and all the other similar posts that way overconfidently state "you don't need k8s" seem to miss the most important factor IMHO: Do you know it or would y
by freedomben 4y ago
This and all the other similar posts that way overconfidently state "you don't need k8s" seem to miss the most important factor IMHO: Do you know it or would you have to learn it?
If you have already been using K8s and you build a side project or launch a new startup, then K8s is probably a great choice for you even if you only have one Deployment and Ingress route. I can take a new app (assuming it already runs in docker) and have it running in a brand new k8s cluster is 20 minutes. I could have it running on a static ec2 instance/linode/droplet/whatever in 30 minutes, but then you have to solve a ton of problems yourself such as CI/CD and deployment automation, etc that k8s gives you for free. K8s is a great choice if you already know how to use it.
This also seems to miss that for startups the best path to k8s is a managed k8s solution. Linode (for example) has one that is wonderfully easy and affordable, and will scale with you a long way.
Lastly, as a person making decisions on tech to use, you are investing in your own future as well. Learning k8s is one of the most useful skill I think a dev can do, behind things like learning bash and standard *nix tools like grep/sed/awk.
Edit (and self-plug): speaking of awk, if you're interested in learning it I put together a free "course", originally a talk I gave at Linux Fest Northwest on awk that I've gotten a lot of positive feedback for. Github: https://github.com/FreedomBen/awk-hack-the-planet https://github.com/FreedomBen/awk-hack-the-planet Youtube: https://youtu.be/43BNFcOdBlY https://youtu.be/43BNFcOdBlY
- JamesSwift 4y agoAs I said in a sibling comment, its not even necessarily that you know k8s or not. Its if you know the underlying _ops_ or not. If someone understands the mechanisms that are being abstracted in k8s then its mostly just a mental mapping of terminology to figure out k8s (not 100% true since there _are_ some k8s idiosyncrasies, but true enough in practice).