Treat Kubernetes clusters as cattle, not pets
At this point, why not just drive it up to the logical conclusion?  Treat your business model as cattle, not pets.  Customers leaving?  Fire up another business until capital runs out, and if it does, no worries, jut hop to another job!<p>Sorry, but I feel like I landed in crazy-land.  Kubernetes is already an exercise in how many layers you can insert with nobody understanding the whole picture.  Ostensibly, it&#x27;s so that you can <i>isolate</i> those fucking jobs so that different teams can run different tasks in the same cluster without interfering with each other.  Hence namespaces, services, resource requirements, port translation, autoscalers, and all those yaml files.<p>It boggles my mind that people look at something like Kubernetes and decide &quot;You know what?  We need more layers.  On top of this.&quot;