Merge pull request #57039 from mburke5678/cma-typos

HPA with custom metrics typo, 4.10, 4.11 & 4.12

Author: mburke5678

modules/nodes-pods-autoscaling-custom-creating-trigger-auth.adoc

@@ -22,8 +22,8 @@ kind: Secret
 metadata:
   name: my-secret
 data:
-  user-name: <base64_username>
-  password: <base64_password>
+  user-name: <base64_USER_NAME>
+  password: <base64_USER_PASSWORD>
 ----
 
 .Procedure
@@ -47,7 +47,7 @@ spec:
     key: USER_NAME
   - parameter: password
     name: my-secret
-    key: PASSWORD
+    key: USER_PASSWORD
 ----
 
 .. Create the `TriggerAuthentication` object:

modules/nodes-pods-autoscaling-custom-creating-workload.adoc

@@ -80,7 +80,7 @@ metadata:
   namespace: my-namespace
 spec:
   scaleTargetRef:
-    api: apps/v1 <3>
+    apiVersion: apps/v1 <3>
     name: example-deployment <4>
     kind: Deployment <5>
     envSourceContainerName: .spec.template.spec.containers[0] <6>

modules/nodes-pods-autoscaling-custom-trigger-auth.adoc

@@ -29,7 +29,7 @@ spec:
     key: USER_NAME <5>
   - parameter: password
     name: my-secret
-    key: PASSWORD
+    key: USER_PASSWORD
 ----
 <1> Specifies the namespace of the object you want to scale.
 <2> Specifies that this trigger authentication uses a secret for authorization.
@@ -48,10 +48,10 @@ spec:
   secretTargetRef: <2>
   - parameter: user-name <3>    
     name: secret-name <4>
-    key: user-name <5>
-  - parameter: password
+    key: USER_NAME <5>
+  - parameter: user-password
     name: secret-name
-    key: user-name
+    key: USER_PASSWORD
 ----
 <1> Note that no namespace is used with a cluster trigger authentication.
 <2> Specifies that this trigger authentication uses a secret for authorization.

modules/nodes-pods-autoscaling-custom-trigger.adoc

@@ -56,7 +56,7 @@ spec:
 <4> Specifies the name to identify the metric in the `external.metrics.k8s.io` API. If you are using more than one trigger, all metric names must be unique.
 <5> Specifies the value to start scaling for.
 <6> Specifies the Prometheus query to use.
-<7> Specifies the authentication method to use. Prometheus scalers support bearer authentication, basic authentication, or TLS authentication. You configure the specific authentication parameters in a trigger authentication, as discussed in a following section. As needed, you can also use a secret.
+<7> Specifies the authentication method to use. Prometheus scalers support bearer authentication (`bearer`), basic authentication (`basic`), or TLS authentication (`tls`). You configure the specific authentication parameters in a trigger authentication, as discussed in a following section. As needed, you can also use a secret.
 <8> Optional: Passes the `X-Scope-OrgID` header to multi-tenant link:https://cortexmetrics.io/[Cortex] or link:https://grafana.com/oss/mimir/[Mimir] storage for Prometheus. This parameter is required only with multi-tenant Prometheus storage, to indicate which data Prometheus should return. 
 <9> Optional: Specifies how the trigger should proceed if the Prometheus target is lost.
      * If `true`, the trigger continues to operate if the Prometheus target is lost. This is the default.