You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-node/1287-in-place-update-pod-resources/README.md
+17-15Lines changed: 17 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,20 +96,20 @@ checklist items _must_ be updated for the enhancement to be released.
96
96
97
97
Items marked with (R) are required *prior to targeting to a milestone / release*.
98
98
99
-
-[] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
100
-
-[] (R) KEP approvers have approved the KEP status as `implementable`
101
-
-[] (R) Design details are appropriately documented
102
-
-[] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
103
-
-[] e2e Tests for all Beta API Operations (endpoints)
104
-
-[] (R) Ensure GA e2e tests for meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
105
-
-[] (R) Minimum Two Week Window for GA e2e tests to prove flake free
106
-
-[] (R) Graduation criteria is in place
107
-
-[] (R) [all GA Endpoints](https://github.com/kubernetes/community/pull/1806) must be hit by [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
99
+
-[x] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
100
+
-[x] (R) KEP approvers have approved the KEP status as `implementable`
101
+
-[x] (R) Design details are appropriately documented
102
+
-[x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
103
+
-[x] e2e Tests for all Beta API Operations (endpoints)
104
+
-[x] (R) Ensure GA e2e tests for meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
105
+
-[x] (R) Minimum Two Week Window for GA e2e tests to prove flake free
106
+
-[x] (R) Graduation criteria is in place
107
+
-[x] (R) [all GA Endpoints](https://github.com/kubernetes/community/pull/1806) must be hit by [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
108
108
-[ ] (R) Production readiness review completed
109
109
-[ ] (R) Production readiness review approved
110
-
-[] "Implementation History" section is up-to-date for milestone
111
-
-[] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
112
-
-[] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
110
+
-[x] "Implementation History" section is up-to-date for milestone
111
+
-[x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
112
+
-[x] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
113
113
114
114
<!--
115
115
**Note:** This checklist is iterative and should be reviewed and updated every time this enhancement is being considered for a milestone.
@@ -822,7 +822,7 @@ be a race condition where the Kubelet may or may not accept the first resize, de
822
822
it admits the first change before seeing the second. This race condition is accepted as working as
823
823
intended.
824
824
825
-
The atomic resize requirement should be reevaluated prior to GA, and in the context of pod-level resources.
825
+
The atomic resize requirement should be reevaluated in the context of pod-level resources.
826
826
827
827
### Actuating Resizes
828
828
@@ -869,7 +869,7 @@ _Version skew note:_ Kubernetes v1.33 (and earlier) nodes only check the pod-lev
869
869
870
870
### Swap
871
871
872
-
Currently (v1.33), if swap is enabled & configured, burstable pods are allocated swap based on their
872
+
Currently (v1.35), if swap is enabled & configured, burstable pods are allocated swap based on their
873
873
memory requests. Since resizing swap requires more thought and additional design, we will forbid
874
874
resizing memory requests of such containers for now. Since the API server is not privy to the node's
875
875
swap configuration, this will be surfaced as resizes being marked `Infeasible`.
@@ -887,7 +887,7 @@ A pod's QOS class is immutable. This is enforced during validation, which requir
887
887
resize the computed QOS Class matches the previous QOS class.
888
888
889
889
[Future enhancements: Mutable QOS Class "Shape"](#mutable-qos-class-shape) proposes a potential
890
-
change to partially relax this restriction, but is removed from Beta scope.
890
+
change to partially relax this restriction, but is removed from the scope of this KEP.
891
891
892
892
[Future enhancements: explicit QOS Class](#design-sketch-explicit-qos-class) proposes an alternative
893
893
enhancement on that, to make QOS class explicit and improve semantics around [workload resource
@@ -1322,6 +1322,7 @@ TODO: Identify more cases
1322
1322
- Resize atomicity
1323
1323
- Exposing allocated resources in the pod status
1324
1324
- QOS class changes
1325
+
- The subset of pod resize tests [here](https://github.com/kubernetes/kubernetes/blob/1aec2eb0030d2f121b4cf78998e9391d9389f1a0/test/e2e/common/node/pod_resize.go) under `doPodResizeTests` and `doPodResizeErrorTests` that meet the Conformance test requirements are promoted to Conformance.
1325
1326
1326
1327
### Upgrade / Downgrade Strategy
1327
1328
Scheduler and API server should be updated before Kubelets in that order.
@@ -1664,6 +1665,7 @@ _This section must be completed when targeting beta graduation to a release._
0 commit comments