Add schedule spec and status for workload

[andyxning]

What would you like to be added:
Currently, kubernetes scheduler supports various scheduling primitives, such as pod affinity/anti-affinity, pod disruption budget, pod topology spread constraints and so on.

Why is this needed:
some scheduling primitives are provided by prefered logical instead of required which may in the lifecycle of the workload, some break variation may happen because pod priority preemption or node pressure eviction.

I think we need to collect the spec and status of the workload pod distribution or the dummy scheduler attribute for every workload and do some alarms when needed.
Describe the solution you'd like
NA. I have not consider a solution about this. Will give it a try in the later weekends.
Additional context
NA

[andyxning]

/triage accepted

[nmn3m]

/assign

[SoumyaRaikwar]

Hi @andyxning, this is a great idea — I'd like to work on this issue.

As a first step, I'm thinking of exposing metrics that describe scheduling-related specs at the workload level, such as:

• Affinity / Anti-affinity presence (boolean flags or counts)
• TopologySpreadConstraints (number defined, maybe with a breakdown by strategy?)
• PodDisruptionBudget references (via annotations or labels, if resolvable)
• Possibly a count of unschedulable pods per workload

This could help operators monitor whether scheduling constraints are drifting from the desired state.