Skip to main content ↑ ↓
Topic: Kubernetes actual use cases? (Read 463 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Kubernetes actual use cases?

I've been using Ansible for a few years now and lately I've been getting more into the whole DevOps in an attempt to put more polish into my systems. As of now I can put webapps and other services behind load balancers and cluster them with GlusterFS/PGSQL without any problems. I've been researching around the last few weeks as to what are considered best practices now and all I keep getting is Kubernetes, Nomad, PaaS stacks and similar solutions. I've been using docker with gitea runners so containers are not scary but is this really what people use nowdays regardless of cluster size? I get that they're potentially useful in the edge case of SUPER LARGE systems that need a complete solution but I see them recommended everywhere.
Even on premises I think that the trivial solution is to get a bunch of servers, install OSes and cluster them up with switches, but what I see the internet recommend is setting up IaaS stacks and kubernetes on top. Is this all noise? What am I missing? I appreciate any feedback.

Re: Kubernetes actual use cases?

Reply #1 –
The benefit of solutions like k8s/nomad and other orchestrators over ansible for applications deployment is that they keep some sort of state where they define where each container is located. This can also simplify the problem of deploying new container since you most likely don't need to specify where to put it. The more different services you have, the more benefit they bring.
As for choosing one, i personally think k8s is better suited for larger scale especially with multiple separated teams involved. Otherwise, nomad is a lot simpler to work with.
ARMtix

Re: Kubernetes actual use cases?

Reply #2 –
Quote from: phoenix_king_rus – on
The benefit of solutions like k8s/nomad and other orchestrators over ansible for applications deployment is that they keep some sort of state where they define where each container is located. This can also simplify the problem of deploying new container since you most likely don't need to specify where to put it. The more different services you have, the more benefit they bring.
As for choosing one, i personally think k8s is better suited for larger scale especially with multiple separated teams involved. Otherwise, nomad is a lot simpler to work with.
What do you think about smaller scale clusters, say with 10 instances and only some dozen services, managed explicitly with ansible without the use of orchestrators? Is there a reason this is so out of fashion?

Re: Kubernetes actual use cases?

Reply #3 –
Quote from: armchaircommander – on
What do you think about smaller scale clusters, say with 10 instances and only some dozen services, managed explicitly with ansible without the use of orchestrators? Is there a reason this is so out of fashion?
I have a similar cluster (in fact it's even less nodes but some services are deployed in 1 or 2 instances) and find it to be really painful to manage when it comes to services migration. Yet, it's too small to install k8s on it. I expect nomad to be perfect solution for such case but for certain reasons can't deploy it there.
ARMtix
 

Re: Kubernetes actual use cases?

Reply #4 –
I've been utilizing Ansible for years and delving deeper into DevOps lately to refine my systems. While I've successfully deployed web apps and services behind load balancers and clustered them with GlusterFS/PGSQL, I'm encountering recommendations for Kubernetes, Nomad, and PaaS stacks. Despite feeling comfortable with Docker and GitLab CI runners, I'm puzzled by the ubiquity of these solutions. Are they truly the norm regardless of cluster size? Setting up IaaS stacks and Kubernetes seems to be favored online, but is this practical for on-premises setups? I'd appreciate any insights.