Source: faun.pub
When Not To Use Kubernetes?Category: Software, Database, Data, Kubernetes, Docker, Infrastructure, automation
This article was originally published on The Chief I/O: When Not To Use Kubernetes? If you engage in technology discussion forums or pay attention to technology news, it feels like everybody is running on Kubernetes or, at least, talking about how they want to move all their workloads to Kubernetes; that they can’t efficiently manage their applications without it.
To efficiently use Kubernetes, you need to learn about containers, network, security, kubernetes specific policies and concepts, and a whole bunch of things that will help you leverage its capabilities.
And if Kubernetes is the best solution for you, you can go ahead and implement it.
You should, in fact, because of its complexities, avoid Kubernetes and only use it if it is the best solution for your use case.
To efficiently use Kubernetes, you need to learn about containers, network, security, kubernetes specific policies and concepts, and a whole bunch of things that will help you leverage its capabilities.
And if Kubernetes is the best solution for you, you can go ahead and implement it.
You should, in fact, because of its complexities, avoid Kubernetes and only use it if it is the best solution for your use case.
Related Articles
Community Partners
DevOps Careers