Skip to content

Commit 20eeb9a

Browse files
committed
Update blog post
1 parent a4fed14 commit 20eeb9a

File tree

2 files changed

+38
-6
lines changed

2 files changed

+38
-6
lines changed
511 KB
Loading

content/en/blog/_posts/2023-04-04-in-place-pod-resize-alpha.md renamed to content/en/blog/_posts/2023-04-04-in-place-pod-resize/index.md

Lines changed: 38 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ date: 2023-04-04
55
slug: in-place-pod-resize-alpha
66
---
77

8-
**Author:** Vinay Kulkarni
8+
**Author:** Vinay Kulkarni (Kubescaler Labs)
99

1010
Kubernetes v1.27 brings a new alpha feature that allows users to resize CPU
1111
and memory resources allocated to pods without restarting them. The `resources`
@@ -25,8 +25,8 @@ Besides the aforementioned resize policy in the pod's spec, a new field named
2525
This field reflects the node resources allocated to the pod's containers.
2626

2727
In addition, a new field called `resources` has been added to the container's
28-
status. This field reflects the actual resource requests and limits that are
29-
configured on the running containers as reported by the container runtime.
28+
status. This field reflects the actual resource requests and limits configured
29+
on the running containers as reported by the container runtime.
3030

3131
Lastly, a new field named `resize` has been added to the pod's status to show the
3232
status of the last requested resize. A value of `Proposed` is an acknowledgement
@@ -42,7 +42,7 @@ resize exceeds the maximum resources the node can ever allocate for a pod.
4242

4343
## When to use this feature
4444

45-
Below are a few examples where this feature may be useful:
45+
Here are a few examples where this feature may be useful:
4646
- Pod is running on node but with either too much or too little resources.
4747
- Pods are not being scheduled do to lack of sufficient CPU or memory in a
4848
cluster that is under-utilized.
@@ -54,7 +54,8 @@ the nodes can be moved.
5454
## How to use this feature
5555

5656
In order to use this feature in v1.27, the `InPlacePodVerticalScaling`
57-
feature gate needs to be enabled.
57+
feature gate must be enabled. A local cluster with this feature enabled
58+
can be started as shown below:
5859

5960
```bash
6061
root@vbuild:~/go/src/k8s.io/kubernetes# FEATURE_GATES=InPlacePodVerticalScaling=true ./hack/local-up-cluster.sh
@@ -93,6 +94,12 @@ Alternatively, you can write to the default kubeconfig:
9394

9495
```
9596

97+
Once the local cluster is up and running, Kubernetes users can schedule pods
98+
with resources and resize the pods via kubectl. An example of how to use this
99+
feature is illustrated in the following demo video.
100+
101+
[![](in-place-pod-resize-demo.png)](https://youtu.be/lYlNfispQBs)
102+
96103

97104
## Example Use Cases
98105

@@ -119,7 +126,32 @@ values at the time of pod creation, and can resize down to normal running
119126
needs once the application has finished initializing.
120127

121128

129+
## Credits
130+
131+
This feature is a result of the efforts of a very collaborative Kubernetes community.
132+
Here's a little shoutout to just a few of the many many people that helped shape
133+
this work.
134+
- @thockin for detail-oriented API design and air-tight code reviews.
135+
- @derekwaynecarr for simplifying the design and thorough API and node reviews.
136+
- @dchen1107 for bringing vast knowledge from Borg and helping us avoid pitfalls.
137+
- @ruiwen-zhao for adding containerd support that enabled full E2E implementation.
138+
- @mikebrow @marosset for reviews on short notice that helped CRI changes make it into v1.25.
139+
- @bobbypage for invaluable help getting CI ready and quickly investigating issues.
140+
- @wangchen615 for implementing comprehensive E2E tests and driving scheduler fixes.
141+
- @Random-Liu for thorough kubelet reviews and identifying problematic race conditions.
142+
- @mrunalp for reviewing cgroupv2 changes and ensuring clean handling of v1 vs v2.
143+
- @Huang-Wei, @ahg-g, @alculquicondor for helping get scheduler changes done.
144+
- @SergeyKanzhelev for shepherding various issues during the home stretch.
145+
- @dashpole for bringing me up to speed on 'the Kubernetes way' of doing things.
146+
- @bsalamat for thoughtful design suggestions that simplified the implementation.
147+
- @dims for being omnipresent and helping make merges happen at critical hours.
148+
- Docs and release teams for helping put the finishing touches on this effort.
149+
150+
And a big thanks to my very supportive management Dr. Xiaoning Ding (ByteDance) and
151+
Dr. Ying Xiong for their patience and encouragement.
152+
153+
122154
## References
123155

124-
TBD-placeholder
156+
TODO: Link to official documentation page
125157

0 commit comments

Comments
 (0)