21–30 of 57 posts
Define “worth it”
I define it as an opportunity cost to learning another technology or language that is in demand in the market. In other words, my perspective is from a career building (increasing total compensation, i.e. $) point of view.
If you plan to manage on-prem Kubernetes clusters, I’d look into the certifications. If you just want to deploy to Kubernetes I wouldn’t bother. In many field basic Kubernetes skills have become expected, but you don’t need the certications to prove it. It may depend on where in the world you’re located.
I have the opportunity to setup a K8s cluster (simple one) on-prem and get it to work. It was an interesting experience. But I'm also cognizant that as more applications are built on top of cloud native services (AWS/Azure/GCP), how relevant then would K8s be?
Much simpler to begin with, smaller footprint/requirements and does 90% of what I have needed.
Earlier quoted context omitted.
I have the opportunity to setup a K8s cluster (simple one) on-prem and get it to work. It was an interesting experience. But I'm also cognizant that as more applications are built on top of cloud native services (AWS/Azure/GCP), how relevant then would K8s be?
On the contrary, as companies rely more and more on the cloud, they chase the mirage of avoiding lock-in even more and k8s plays a big role in this
With your ML background I'd probably focus on things like AWS Sagemaker and going from dev to prod in a sensible fashion.
I didn't get the memo that k8s has gone out of fashion since last year. If you're in devops, you will eventually have to deal with k8s. There's no need to go very deep into it unless you want to, but you are expected in this day and age to have at least basic familiarity with it.
That's not exactly true though. You can do "DevOps" and horizontal scaling (or simply no scaling) by other means too. K8s may be the best for large deployments overall, but it's not a requirement. Lots of companies run large scale services without k8s.
Lots more do so using k8s.
The question is "is it worth learning it?" And the answer is yes. It's not wasted time or energy to learn the most popular and du-jour orchestration system.
No. Useless and overly complicated.
What's the alternative?
I didn't get the memo that k8s has gone out of fashion since last year. If you're in devops, you will eventually have to deal with k8s. There's no need to go very deep into it unless you want to, but you are expected in this day and age to have at least basic familiarity with it.
That's not exactly true though. You can do "DevOps" and horizontal scaling (or simply no scaling) by other means too. K8s may be the best for large deployments overall, but it's not a requirement. Lots of companies run large scale services without k8s.