Provide transparency with cluster autoscaling

[abbi-gaurav]

Description

Many customers who are having big clusters (with large number of worker nodes) are always looking to optimize usage. They try out various scale down mechanism using KEDA / HPA.
The challenge faced by them is the clusters do not scale down even after they have sufficiently scaled down their microservices.
Moreover, there is no clear information as to why the cluster did not scale down.

What customers are looking for?

• What are the right configurations and practices that would enable cluster scale down when apps are scaled down?
• How to make it transparent to them when scale down happened or if it was prevented, what was the cause?

External link: https://github.tools.sap/kyma/backlog/issues/6116

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[ingentismg]

We are still very much interested in this.
Right now, we are again in the situation, where a cluster does not scale down and we have no idea why.