@@ -24,7 +24,7 @@ To get started with this template:
24
24
appropriate SIG(s).
25
25
- [x] **Create a PR for this KEP.**
26
26
Assign it to people in the SIG who are sponsoring this process.
27
- - [ ] **Merge early and iterate.**
27
+ - [x ] **Merge early and iterate.**
28
28
Avoid getting hung up on specific details and instead aim to get the goals of
29
29
the KEP clarified and merged quickly. The best way to do this is to just
30
30
start with the high-level sections and fill out details incrementally in
@@ -129,11 +129,11 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
129
129
- [x] (R) Design details are appropriately documented
130
130
- [x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
131
131
- [x] (R) Graduation criteria is in place
132
- - [ ] (R) Production readiness review completed
133
- - [ ] (R) Production readiness review approved
132
+ - [x ] (R) Production readiness review completed
133
+ - [x ] (R) Production readiness review approved
134
134
- [x] "Implementation History" section is up-to-date for milestone
135
- - [ ] User-facing documentation has been created in [ kubernetes/website] , for publication to [ kubernetes.io]
136
- - [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
135
+ - [x ] User-facing documentation has been created in [ kubernetes/website] , for publication to [ kubernetes.io]
136
+ - [x ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
137
137
138
138
<!--
139
139
**Note:** This checklist is iterative and should be reviewed and updated every time this enhancement is being considered for a milestone.
@@ -349,7 +349,7 @@ type PodAffinityTerm struct {
349
349
// The term is applied to the union of the namespaces selected by this field
350
350
// and the ones listed in the namespaces field.
351
351
// nil selector and empty namespaces list means "this pod's namespace"
352
- // An empty selector ({}) is not valid .
352
+ // An empty selector ({}) means all namespaces .
353
353
NamespaceSelector *metav1.LabelSelector
354
354
}
355
355
` ` `
@@ -583,6 +583,25 @@ _This section must be completed when targeting beta graduation to a release._
583
583
* **How can an operator determine if the feature is in use by workloads?**
584
584
The operator can query pods with the NamespaceSelector field set in pod affinity terms.
585
585
586
+ * **How can someone using this feature know that it is working for their instance?**
587
+ <!--
588
+ For instance, if this is a pod-related feature, it should be possible to determine if the feature is functioning properly
589
+ for each individual pod.
590
+ Pick one more of these and delete the rest.
591
+ Please describe all items visible to end users below with sufficient detail so that they can verify correct enablement
592
+ and operation of this feature.
593
+ Recall that end users cannot usually observe component logs or access metrics.
594
+ -->
595
+
596
+ - [x] Other (treat as last resort)
597
+ - Details : inter-pod affinity as a feature doesn't trigger pod status updates on its own,
598
+ none of the scheduler's filters/scores do on their own. If a pod using affinity
599
+ was successfully assigned a node, nodeName will be updated, if not, then
600
+ PodScheduled condition will be false, and an event will be recorded with a detailed
601
+ message describing the reason including the failed filters (inter-pod affnity could
602
+ be one of them).
603
+
604
+
586
605
* **What are the SLIs (Service Level Indicators) an operator can use to determine
587
606
the health of the service?**
588
607
- [x] Metrics
@@ -686,6 +705,7 @@ information to express the idea and why it was not acceptable.
686
705
- 2021-01-11 : Initial KEP sent for review
687
706
- 2021-02-10 : Remove the restriction on empty namespace selector
688
707
- 2021-04-26 : Graduate the feature to Beta
708
+ - 2022-01-08 : Graduate the feature to Stable
689
709
690
710
<!--
691
711
Major milestones in the lifecycle of a KEP should be tracked in this section.
0 commit comments