Merge pull request #31276 from mburke5678/vpa-fix-formatting

Fixed formatting in a VPA module

Author: mburke5678

modules/nodes-pods-vertical-autoscaler-using-about.adoc

@@ -94,7 +94,8 @@ The output shows the recommended resources, `target`, the minimum recommended re
 
 The VPA uses the `lowerBound` and `upperBound` values to determine if a pod needs to be updated. If a pod has resource requests below the `lowerBound` values or above the `upperBound` values, the VPA terminates and recreates the pod with the `target` values.
 
-Automatically applying VPA recommendations::
+[id="nodes-pods-vertical-autoscaler-using-auto_{context}"]
+== Automatically applying VPA recommendations
 To use the VPA to automatically update pods, create a VPA CR for a specific workload object with `updateMode` set to `Auto` or `Recreate`.
 
 When the pods are created for the workload object, the VPA constantly monitors the containers to analyze their CPU and memory needs. The VPA deletes and redeploys pods with new container resource limits and requests to meet those needs, honoring any Pod Disruption Budget set for your applications. The recommendations are added to the `status` field of the VPA CR for reference.
@@ -125,7 +126,8 @@ spec:
 There must be operating pods in the project before the VPA can determine recommended resources and apply the recommendations to new pods.
 ====
 
-Automatically applying VPA recommendations on pod creation::
+[id="nodes-pods-vertical-autoscaler-using-pod_{context}"]
+== Automatically applying VPA recommendations on pod creation
 To use the VPA to apply the recommended resources only when a pod is first deployed, create a VPA CR for a specific workload object with `updateMode` set to `Initial`.
 
 When the pods are created for that workload object, the VPA analyzes the CPU and memory needs of the containers and assigns the recommended container resource limits and requests. The VPA does not update the pods as it learns new resource recommendations.
@@ -154,7 +156,9 @@ spec:
 There must be operating pods in the project before a VPA can determine recommended resources and apply the recommendations to new pods.
 ====
 
-Manually applying VPA recommendations::
+[id="nodes-pods-vertical-autoscaler-using-manual_{context}"]
+== Manually applying VPA recommendations
+
 To use the VPA to only determine the recommended CPU and memory values, create a VPA CR for a specific workload object with `updateMode` set to `off`.
 
 When the pods are created for that workload object, the VPA analyzes the CPU and memory needs of the containers and records those recommendations in the `status` field of the VPA CR. The VPA does not update the pods as it determines new resource recommendations.
@@ -192,7 +196,9 @@ With the recommendations, you can edit the workload object to add CPU and memory
 There must be operating pods in the project before a VPA can determine recommended resources.
 ====
 
-Exempting containers from applying VPA recommendations::
+[id="nodes-pods-vertical-autoscaler-using-exempt_{context}"]
+== Exempting containers from applying VPA recommendations
+
 If your workload object has multiple containers and you do not want the VPA to evaluate and act on all of the containers, create a VPA CR for a specific workload object and add a `resourcePolicy` to opt-out specific containers.
 
 When the VPA updates the pods with recommended resources, any containers with a `resourcePolicy` are not updated and the VPA does not present recommendations for those containers in the pod.