Question 1

What problem does the proposed approach address in Kubernetes scheduling?

Accepted Answer

The approach targets Kubernetes’ default static scheduling, which ignores runtime cluster and microservice resource usage, leading to resource contention and worse application response time.

Question 2

How does the load-aware orchestration strategy work?

Accepted Answer

It orchestrates microservice applications dynamically using real-time resource usage patterns and continuously re-adjusts placement as infrastructure and application states change.

Question 3

What benefits are reported compared with the standard Kubernetes scheduler?

Accepted Answer

A prototype evaluation in a testbed demonstrates substantial benefits, including improved application performance while enabling higher application colocation on the same cluster and maintaining acceptable response times.