I've had this happen in the real world. In this case it was a GraphQL implementation that gradually grew in size, complexity and scope. The team maintaining it

I've had this happen in the real world. In this case it was a GraphQL implementation that gradually grew in size, complexity and scope. The team maintaining it never adjusted the initial resource requirements within about 2 years because it has never been a problem - until a different (much larger by total CPU allocated) service started consuming all the bursting it could get and the GraphQL service just stopped processing requests. Before any autoscaling could kick in, it went into CrashLoopBackoff with failing liveness. You can and should catch such cases early with monitoring, but our platform team was extremely tiny, especially for how many developers it served.