Skip to content

Commit be366b2

Browse files
committed
Typeos.
1 parent 9b06685 commit be366b2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

keps/sig-node/5620-resizing-balloon/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
165165
We provide a resizable node through the use of balloon pods, which acquire, but do not use, resources to ensure that pods on
166166
the node cannot consume more than the current size of the node. This allows us to effectively use IPPR to resize
167167
the node, in addition to using it to resize pods. To decrease the size of a given node, an agent in the system can
168-
upsize the balloon pod on the given node. To increase the size of a given node, an agent in the sytem can downsize
168+
upsize the balloon pod on the given node. To increase the size of a given node, an agent in the system can downsize
169169
the balloon pod on the given node, allowing other pods to consume more resources on the node itself.
170170

171171
## Motivation
@@ -189,7 +189,7 @@ Note that while this feature is superficially simlar to hotplug, it is orthogona
189189

190190
## Proposal
191191

192-
We propose that Kubernetes provide an official "balloon pod" concept. Balloon pods are deployed to each node in the sytem using a daemon set controller which can be enabled or disabled by administrators on a given cluster. Balloon pods claim resources using requests, but then do not consume them. This allows the underlying infrastructure to provide only the resources that are unused by the balloons, in whatever way the infrastructure feels appropriate.
192+
We propose that Kubernetes provide an official "balloon pod" concept. Balloon pods are deployed to each node in the system using a daemon set controller which can be enabled or disabled by administrators on a given cluster. Balloon pods claim resources using requests, but then do not consume them. This allows the underlying infrastructure to provide only the resources that are unused by the balloons, in whatever way the infrastructure feels appropriate.
193193

194194
To resize a given node, a scaling component can simply invoke in-place-pod-updates on the resources for the balloon pod. To "upsize" the node the component would "downsize" the balloon pod to release more resources to the pods on the node. To "downsize" the node the component would "upsize" the ballon pod to remove resources from the pool available to the pods on the node.
195195

0 commit comments

Comments
 (0)