K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The tool can automate almost any workflow and infrastructure consumption. It has state of the art develop and support with great online training, online full manual set, and a comprehensive support team and network of SIs/VARS that are very qualified.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
VMware is too hard to use, too expensive to support, and not a full lifecycle tool for workflows and Infrastructure (no support of physical either). AWS or Azure or Google solutions are good if you are only in the cloud and only using their tools. Not good if you have on-prem or non-Cloud based tools/infrastructure. Build it yourself automation frameworks can be good for people with unlimited funds, but they are not the best way to go and missing many capabilities typically.
