Off the top of my head: * you’re not using GCP * you have workloads that don’t mesh well with common cloud PaaS patterns * you want to pick-and-choose your c

Off the top of my head: * you’re not using GCP * you have workloads that don’t mesh well with common cloud PaaS patterns * you want to pick-and-choose your cloud dependencies * you want to use a commodity tech-stack so that hiring, tooling and support are far more readily available. All of this comes with the obvious caveat of: sure, if you aren’t having issues, or reaching the limits of whatever PaaS solution you’re currently using, then don’t swap unnecessarily, but that still means there’s a lot of useful features that K8s offers.