Answer the question
In order to leave comments, you need to log in
Does it make sense to migrate the internal infrastructure to Kubernetes?
Does it make sense to transfer internal infrastructure (jira, jenkins, gitlab, buld agents, test servers, database servers, etc.) from virtualization systems to Kubernetes? Your iron.
Answer the question
In order to leave comments, you need to log in
Kubernetes is hard. It's not for stateful applications, it's a bunch of hard-to-fix problems, it's updates without backwards compatibility, it's a bunch of additional layers of abstraction, it's a step away from the "next-next-finish" instruction - and oh, that's it. And it's also a single point of failure, even if it's in a cluster.
It makes sense to use kubernetes for tasks that require easy scaling, rolling-update and other goodies that are usually typical for large web projects. Of the things you listed, it only makes sense to drag build agents to kubernetes, and then if it already exists, and not deploy a cluster for them.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question