@@ -98,7 +98,7 @@ we aim to simplify access to this information for Pods via the Downward API.
98
98
99
99
### Goals
100
100
101
- * Values from Node labels ` topology.k8s .io/zone ` , ` topology.k8s .io/region ` and ` kubernetes.io/hostname ` are made
101
+ * Values from Node labels ` topology.kubernetes .io/zone ` , ` topology.kubernetes .io/region ` and ` kubernetes.io/hostname ` are made
102
102
available via downward API
103
103
* Additional node labels can be made available via downward API using admission webhooks that mutate ` pods/binding ` .
104
104
@@ -225,7 +225,8 @@ E2E tests will also ensure behavior is exercised when the feature gate is enable
225
225
226
226
#### Beta
227
227
228
- TODO after Alpha.
228
+ - Fix standard topology label used in PodTopologyLabels admission controller (topology.k8s.io -> topology.kubernetes.io)
229
+ - Unit, integration and e2e tests
229
230
230
231
#### GA
231
232
@@ -290,7 +291,9 @@ Tests will be added to ensure feature gate works as expected.
290
291
291
292
### Rollout, Upgrade and Rollback Planning
292
293
293
- TODO for Beta.
294
+ Manual testing will be exercised to ensure that PodTopologyLabelsAdmission can be enabled and then disabled.
295
+ When disabled, existing Pods with topology labels will continue to run with those labels and new Pods will no longer
296
+ container topology labels.
294
297
295
298
###### How can a rollout or rollback fail? Can it impact already running workloads?
296
299
@@ -402,6 +405,7 @@ Revert feature gate and stop consuming downward API.
402
405
## Implementation History
403
406
404
407
- ` v1.33 ` : initial KEP is accepeted and alpha implementation is complete
408
+ - ` v1.34 ` : fix topology labels from topology.k8s.io to topology.kubernetes.io.
405
409
406
410
## Drawbacks
407
411
0 commit comments