diff --git a/modules/nodes-pods-vertical-autoscaler-about.adoc b/modules/nodes-pods-vertical-autoscaler-about.adoc index 6d9f95eecf0c..c0b7d4a18504 100644 --- a/modules/nodes-pods-vertical-autoscaler-about.adoc +++ b/modules/nodes-pods-vertical-autoscaler-about.adoc @@ -12,7 +12,7 @@ You can use the default recommender or use your own alternative recommender to a The default recommender automatically computes historic and current CPU and memory usage for the containers in those pods and uses this data to determine optimized resource limits and requests to ensure that these pods are operating efficiently at all times. For example, the default recommender suggests reduced resources for pods that are requesting more resources than they are using and increased resources for pods that are not requesting enough. -The VPA then automatically deletes any pods that are out of alignment with these recommendations one at a time, so that your applications can continue to serve requests with no downtime. The workload objects then re-deploy the pods with the original resource limits and requests. The VPA uses a mutating admission webhook to update the pods with optimized resource limits and requests before the pods are admitted to a node. If you do not want the VPA to delete pods, you can view the VPA resource limits and requests and manually update the pods as needed. +The VPA then automatically deletes any pods that are out of alignment with these recommendations one at a time, so that your applications can continue to serve requests with no downtime. The workload objects then redeploy the pods with the original resource limits and requests. The VPA uses a mutating admission webhook to update the pods with optimized resource limits and requests before the pods are admitted to a node. If you do not want the VPA to delete pods, you can view the VPA resource limits and requests and manually update the pods as needed. [NOTE] ==== @@ -27,5 +27,5 @@ Administrators can use the VPA to better utilize cluster resources, such as prev [NOTE] ==== -If you stop running the VPA or delete a specific VPA CR in your cluster, the resource requests for the pods already modified by the VPA do not change. Any new pods get the resources defined in the workload object, not the previous recommendations made by the VPA. +If you stop running the VPA or delete a specific VPA CR in your cluster, the resource requests for the pods already modified by the VPA do not change. However, any new pods get the resources defined in the workload object, not the previous recommendations made by the VPA. ==== diff --git a/modules/nodes-pods-vertical-autoscaler-custom.adoc b/modules/nodes-pods-vertical-autoscaler-custom.adoc index a91fbe0fac9d..4e175b95fc54 100644 --- a/modules/nodes-pods-vertical-autoscaler-custom.adoc +++ b/modules/nodes-pods-vertical-autoscaler-custom.adoc @@ -14,7 +14,7 @@ For example, the default recommender might not accurately predict future resourc [NOTE] ==== -Instructions for how to create a recommender are beyond the scope of this documentation, +Instructions for how to create a recommender are beyond the scope of this documentation. ==== .Procedure diff --git a/modules/nodes-pods-vertical-autoscaler-using-about.adoc b/modules/nodes-pods-vertical-autoscaler-using-about.adoc index 4e1569d7ab44..dcd97f025d21 100644 --- a/modules/nodes-pods-vertical-autoscaler-using-about.adoc +++ b/modules/nodes-pods-vertical-autoscaler-using-about.adoc @@ -267,7 +267,7 @@ spec: <1> The type of workload object you want this VPA CR to manage. <2> The name of the workload object you want this VPA CR to manage. <3> Set the mode to `Auto`, `Recreate`, `Initial`, or `Off`. The `Recreate` mode should be used rarely, only if you need to ensure that the pods are restarted whenever the resource request changes. -<4> Specify the containers you want to opt-out and set `mode` to `Off`. +<4> Specify the containers that you do not want updated by the VPA and set the `mode` to `Off`. For example, a pod has two containers, the same resource requests and limits: