openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Code Issues Releases Activity

OCPBUGS-30166:correcting typos

Browse Source
This commit is contained in:
Brendan Daly
2024-03-08 16:43:32 +00:00
parent a55044ae64
commit 423fc297ee
4 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
modules/nodes-pods-vertical-autoscaler-about.adoc
View File

@@ -8,6 +8,17 @@
The Vertical Pod Autoscaler Operator (VPA) is implemented as an API resource and a custom resource (CR). The CR determines the actions the Vertical Pod Autoscaler Operator should take with the pods associated with a specific workload object, such as a daemon set, replication controller, and so forth, in a project.
The VPA Operator consists of three components, each of which has its own pod in the VPA namespace:
Recommender::
The VPA recommender monitors the current and past resource consumption and, based on this data, determines the optimal CPU and memory resources for the pods in the associated workload object.
Updater::
The VPA updater checks if the pods in the associated workload object have the correct resources. If the resources are correct, the updater takes no action. If the resources are not correct, the updater kills the pod so that they can be recreated by their controllers with the updated requests.
Admission controller::
The VPA admission controller sets the correct resource requests on each new pod in the associated workload object, whether the pod is new or was recreated by its controller due to the VPA updater actions.
You can use the default recommender or use your own alternative recommender to autoscale based on your own algorithms.
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.
@@ -16,7 +27,7 @@ The VPA then automatically deletes any pods that are out of alignment with these
[NOTE]
====
By default, workload objects must specify a minimum of two replicas in order for the VPA to automatically delete their pods. Workload objects that specify fewer replicas than this minimum are not deleted. If you manually delete these pods, when the workload object redeploys the pods, the VPA does update the new pods with its recommendations. You can change this minimum by modifying the `VerticalPodAutoscalerController` object as shown shown in _Changing the VPA minimum value_.
By default, workload objects must specify a minimum of two replicas in order for the VPA to automatically delete their pods. Workload objects that specify fewer replicas than this minimum are not deleted. If you manually delete these pods, when the workload object redeploys the pods, the VPA does update the new pods with its recommendations. You can change this minimum by modifying the `VerticalPodAutoscalerController` object as shown in _Changing the VPA minimum value_.
====
For example, if you have a pod that uses 50% of the CPU but only requests 10%, the VPA determines that the pod is consuming more CPU than requested and deletes the pod. The workload object, such as replica set, restarts the pods and the VPA updates the new pod with its recommended resources.

2
modules/nodes-pods-vertical-autoscaler-custom.adoc
View File

@@ -70,7 +70,7 @@ subjects:
name: alt-vpa-recommender-sa
namespace: <namespace_name>
----
<1> Creates a service accocunt for the recommender in the namespace where the recommender is deployed.
<1> Creates a service account for the recommender in the namespace where the recommender is deployed.
<2> Binds the recommender service account to the `metrics-reader` role. Specify the namespace where the recommender is to be deployed.
<3> Binds the recommender service account to the `vpa-actor` role. Specify the namespace where the recommender is to be deployed.
<4> Binds the recommender service account to the `vpa-target-reader` role. Specify the namespace where the recommender is to be deployed.

2
modules/nodes-pods-vertical-autoscaler-install.adoc
View File

@@ -43,7 +43,7 @@ is automatically created if it does not exist.
$ oc get all -n openshift-vertical-pod-autoscaler
----
+
The output shows four pods and four deplyoments:
The output shows four pods and four deployments:
+
.Example output
[source,terminal]

2
modules/nodes-pods-vertical-autoscaler-using-about.adoc
View File

@@ -134,7 +134,7 @@ When the pods are created for the workload object, the VPA constantly monitors t
[NOTE]
====
By default, workload objects must specify a minimum of two replicas in order for the VPA to automatically delete their pods. Workload objects that specify fewer replicas than this minimum are not deleted. If you manually delete these pods, when the workload object redeploys the pods, the VPA does update the new pods with its recommendations. You can change this minimum by modifying the `VerticalPodAutoscalerController` object as shown shown in _Changing the VPA minimum value_.
By default, workload objects must specify a minimum of two replicas in order for the VPA to automatically delete their pods. Workload objects that specify fewer replicas than this minimum are not deleted. If you manually delete these pods, when the workload object redeploys the pods, the VPA does update the new pods with its recommendations. You can change this minimum by modifying the `VerticalPodAutoscalerController` object as shown in _Changing the VPA minimum value_.
====
.Example VPA CR for the `Auto` mode