KEP-3633keps/sig-scheduling/3633-matchlabelkeys-to-podaffinity
Introduce MatchLabelKeys and MismatchLabelKeys to PodAffinity and PodAntiAffinity
<!-- This section is incredibly important for producing high-quality, user-focused documentation such as release notes or a development roadmap. It should be possible to collect this information before implementation begins, in order to avoid requiring implementors to split their attention between writing release notes and implementing the feature itself. KE… Full summary
<!-- This section is incredibly important for producing high-quality, user-focused documentation such as release notes or a development roadmap. It should be possible to collect this information before implementation begins, in order to avoid requiring implementors to split their attention between writing release notes and implementing the feature itself. KEP editors and SIG Docs should help to ensure that the tone and content of the Summary section is useful for a wide audience. A good summary is probably at least a paragraph in length. Both in this section and below, follow the guidelines of the [documentation style guide]. In particular, wrap lines to a reasonable length, to make it easier for reviewers to cite specific portions, and to minimize diff churn on updates. [documentation style guide]: https://github.com/kubernetes/community/blob/master/contributors/guide/style-guide.md --> This KEP proposes introducing a complementary field MatchLabelKeys to PodAffinityTerm. This enables users to finely control the scope where Pods are expected to co-exist (PodAffinity) or not (PodAntiAffinity), on top of the existing LabelSelector.
Facts
- Authors
- @sanposhiho
- Approvers
- @huang-wei
- Reviewers
- @huang-wei
- Tracking issue
- #3633(opens GitHub in a new tab) closedcompletedclosed 2025-05-19 07:14 UTCmilestone v1.33sig/schedulingstage/stable
- Milestones
- alpha v1.29beta v1.31stable v1.33
- Participating SIGs
- none
- Feature gates
- MatchLabelKeysInPodAffinity
- Created / last updated
- 2022-11-09 / none