When to *not* use Kubernetes in DevOps

Kubernetes (k8s) has become the darling of DevOps, and for good reason. It offers power and flexibility for deploying and managing applications at scale. But is it _always_ the right tool for the job?
TL;DW: Noooooo.
0:00 Introduction
1:05 Components of Kubernetes you must manage
2:15 Defining the criteria for using Kubernetes
2:45 What to do if you don't have resources to manage Kubernetes
3:35 What applications are good candidates for Kubernetes?
4:20 What applications are not good candidates for Kubernetes?
4:50 Alternatives to Kubernetes

================================================
Links:

[davidsun]

Too many folks pushing resume driven architectures. Reality is most people don't have these Google sized scaling issues and don't need to burden themselves with all these additional/complicated abstractions.

[overstandnigeria]

Thank you for this. You just reenforced my convictions. Fargat hits the sweet spot of ease of use and scalability that I need.

[bakamarimo]

Thanks for the video,
Quality content.
Definitely deserve more subs

[astor]

Great video as always. Is it a good practice to have mid/large applications on same k8s cluster separated by namespace. And, is prometheus+grafana only for monitoring cluster or is it also meant to be for monitoring applications that are running inside cluster? Don't know if having dedicated prometheus+grafana that is running outside cluster to monitor applications a smart move. Really looking forward to your reply :)

[judgewest]

When not to use Kubernetes - all the time!