What you would like to be added?
Introduce a new condition at the PodCliqueSet that indicates that one or more TopologyDomains that are referenced from within a running PCS workload are removed from the ClusterTopology.
Why is this needed?
It is possible that a cluster admin/operator updates Grove OperatorConfiguration.TopologyAwareScheduling.Levels by removing some TopologyDomain's that are used by already running workloads (PCS). While this has no impact on running workload pods, it can have an impact on recreated Pods due to evictions, crashes etc. Therefore it is important to bring the visibility that one or more of required TopologyConstraints that are defined in PCS can no longer be met.
What you would like to be added?
Introduce a new condition at the
PodCliqueSetthat indicates that one or more TopologyDomains that are referenced from within a running PCS workload are removed from theClusterTopology.Why is this needed?
It is possible that a cluster admin/operator updates Grove
OperatorConfiguration.TopologyAwareScheduling.Levelsby removing some TopologyDomain's that are used by already running workloads (PCS). While this has no impact on running workload pods, it can have an impact on recreated Pods due to evictions, crashes etc. Therefore it is important to bring the visibility that one or more of required TopologyConstraints that are defined in PCS can no longer be met.