Consider that I have two pods: one is serving webpages and another is performing consistent computation, like a Flask server on one pod and a Spark Executor as the other.
Suddenly a new feature creates lots of traffic for a specific route on the Flask server. Normally the Executor is numeric and consistent and the Flask server is sparse and memory/IO bound but this causes the workloads to be very similar and stalls the CPU on this Node.
Can Kubernetes' scheduler identify this and reschedule the pod?