Add NamespaceSelector to pod affinity spec

[ahg-g]

What would you like to be added:
Pod affinity is currently scoped to the pod namespace by default, but users could specify a list of namespaces as well.

We are proposing to add a namespaceSelector *metav1.LabelSelector so that it is easier for users to specify the set of namespaces that pod affinity applies to without explicitly listing them.

Why is this needed:
Makes it possible to specify patterns of namespaces that the pod affinity constraints applies to. This is especially useful when trying to force 1:1 pod to node placement for example across namespaces.

• approved KEP (Add KEP for Pod Affinity NamespaceSelector enhancements#2251)
• API PR (Add PodAffinityTerm.NamespaceSelector and CrossNamespacePodAffinity Quota scope APIs #98378)
• Implementation for CrossNamespacePodAffinity quota scope (Implements CrossNamespacePodAffinity quota scope #98582)
• Implementation in inter-pod affinity plugin (Implements CrossNamespacePodAffinity quota scope #98582)
• Integrate PodInfo into QueuedPodInfo
• Performance integration tests (Added benchmarks for pod affinity NamespaceSelector #101329)

/sig scheduling

[k8s-ci-robot]

@ahg-g: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[SataQiu]

/cc

[ahg-g]

/close

[k8s-ci-robot]

@ahg-g: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.