1) It will take you longer than you think
2) It will be harder than you imagined
3) It’s harder to find people who know it and non-trivial to get good at it (this should have been closer to the top) your project can be done in six months by five k8s experts but you only found one dude who knows it and he’s more a’ight than pro.
It’s probably still worth it, just go in with your eyes open.
Be prepared for this unfortunate pattern: “this thing I want just doesn’t work and probably never will.
Deploying k8s on a small, self-contained project that you just want to set up and go forever is probably a good place to begin.
If you try to move your whole production workflow in one go...
You’re going to have a bad time.
> 1) It will take you longer than you think 2) It will be harder than you imagined 3) It’s harder to find people who know it
Just so people have an idea of how hard it is to find people. I've got just about 1 year of experience getting kubernetes into production at a very large (multi-billion dollar) company. I have so many job offers coming in that I'm not even talking to companies offering less than 350k total comp. I don't have a college degree and 5 years ago I was making $50k a year. That might be just the generally bubble-ish nature of the tech industry right now, but if they're throwing around that kind of money for someone like me, I imagine that small shops have no way to compete.
Any chance you'd be happy to elaborate on what your role is? Are you primarily part of a dev-ops team, or tackling Kubernetes as part of developing the product? Did you obtain CNCF certification / think there's much value in those?
Also, if _all_ you want to deploy is a small, self-contained project, you don't need k8s. Most small companies/startups just don't need it. Stick with what is simple.
1) It will take you longer than you think 2) It will be harder than you imagined 3) It’s harder to find people who know it and non-trivial to get good at it (this should have been closer to the top) your project can be done in six months by five k8s experts but you only found one dude who knows it and he’s more a’ight than pro.
It’s probably still worth it, just go in with your eyes open.
Be prepared for this unfortunate pattern: “this thing I want just doesn’t work and probably never will.
Deploying k8s on a small, self-contained project that you just want to set up and go forever is probably a good place to begin. If you try to move your whole production workflow in one go... You’re going to have a bad time.