Merge pull request #38503 from mburke5678/service.alpha.openshift.io

Change `service.alpha.openshift.io` to `service.beta.openshift.io`

Author: mburke5678

modules/builds-service-serving-certificate-secrets.adoc

@@ -10,11 +10,11 @@ Service serving certificate secrets are intended to support complex middleware a
 
 To secure communication to your service, have the cluster generate a signed serving certificate/key pair into a secret in your namespace.
 
-* Set the `service.alpha.openshift.io/serving-cert-secret-name` annotation on your service with the value set to the name you want to use for your secret.
+* Set the `service.beta.openshift.io/serving-cert-secret-name` annotation on your service with the value set to the name you want to use for your secret.
 +
 Then, your `PodSpec` can mount that secret. When it is available, your pod runs. The certificate is good for the internal service DNS name, `<service.name>.<service.namespace>.svc`.
 +
-The certificate and key are in PEM format, stored in `tls.crt` and `tls.key` respectively. The certificate/key pair is automatically replaced when it gets close to expiration. View the expiration date in the `service.alpha.openshift.io/expiry` annotation on the secret, which is in RFC3339 format.
+The certificate and key are in PEM format, stored in `tls.crt` and `tls.key` respectively. The certificate/key pair is automatically replaced when it gets close to expiration. View the expiration date in the `service.beta.openshift.io/expiry` annotation on the secret, which is in RFC3339 format.
 
 [NOTE]
 ====

modules/builds-troubleshooting-service-certificate-generation.adoc

@@ -8,7 +8,7 @@
 If your request for access to resources is denied:
 
 Issue::
-If a service certificate generation fails with (service's `service.alpha.openshift.io/serving-cert-generation-error` annotation contains):
+If a service certificate generation fails with (service's `service.beta.openshift.io/serving-cert-generation-error` annotation contains):
 
 .Example output
 [source,terminal]
@@ -17,7 +17,7 @@ secret/ssl-key references serviceUID 62ad25ca-d703-11e6-9d6f-0e9c0057b608, which
 ----
 
 Resolution::
-The service that generated the certificate no longer exists, or has a different `serviceUID`. You must force certificates regeneration by removing the old secret, and clearing the following annotations on the service: `service.alpha.openshift.io/serving-cert-generation-error` and `service.alpha.openshift.io/serving-cert-generation-error-num`:
+The service that generated the certificate no longer exists, or has a different `serviceUID`. You must force certificates regeneration by removing the old secret, and clearing the following annotations on the service: `service.beta.openshift.io/serving-cert-generation-error` and `service.beta.openshift.io/serving-cert-generation-error-num`:
 
 [source,terminal]
 ----
@@ -26,12 +26,12 @@ $ oc delete secret <secret_name>
 
 [source,terminal]
 ----
-$ oc annotate service <service_name> service.alpha.openshift.io/serving-cert-generation-error-
+$ oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-
 ----
 
 [source,terminal]
 ----
-$ oc annotate service <service_name> service.alpha.openshift.io/serving-cert-generation-error-num-
+$ oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-num-
 ----
 
 [NOTE]

modules/configuring-dynamic-admission.adoc

@@ -257,7 +257,7 @@ items:
     namespace: my-webhook-namespace
     name: server
     annotations:
-      service.alpha.openshift.io/serving-cert-secret-name: server-serving-cert
+      service.beta.openshift.io/serving-cert-secret-name: server-serving-cert
   spec:
     selector:
       server: "true"

modules/monitoring-exposing-custom-application-metrics-for-horizontal-pod-autoscaling.adoc

@@ -148,7 +148,7 @@ apiVersion: v1
 kind: Service
 metadata:
   annotations:
-    service.alpha.openshift.io/serving-cert-secret-name: prometheus-adapter-tls
+    service.beta.openshift.io/serving-cert-secret-name: prometheus-adapter-tls
   labels:
     name: prometheus-adapter
   name: prometheus-adapter

modules/nodes-pods-secrets-certificates-about.adoc

@@ -22,7 +22,7 @@ kind: Service
 metadata:
   name: registry
   annotations:
-    service.alpha.openshift.io/serving-cert-secret-name: registry-cert<1>
+    service.beta.openshift.io/serving-cert-secret-name: registry-cert<1>
 # ...
 ----
 <1> Specify the name for the certificate

modules/nodes-pods-secrets-certificates-creating.adoc

@@ -6,15 +6,15 @@
 = Generating signed certificates for use with secrets
 
 To use a signed serving certificate/key pair with a pod, create or edit the service to add
-the `service.alpha.openshift.io/serving-cert-secret-name` annotation, then add the secret to the pod.
+the `service.beta.openshift.io/serving-cert-secret-name` annotation, then add the secret to the pod.
 
 .Procedure
 
 To create a _service serving certificate secret_:
 
 . Edit the `Pod` spec for your service.
 
-. Add the `service.alpha.openshift.io/serving-cert-secret-name` annotation
+. Add the `service.beta.openshift.io/serving-cert-secret-name` annotation
 with the name you want to use for your secret.
 +
 [source,yaml]
@@ -24,7 +24,7 @@ apiVersion: v1
 metadata:
   name: my-service
   annotations:
-      service.alpha.openshift.io/serving-cert-secret-name: my-cert <1>
+      service.beta.openshift.io/serving-cert-secret-name: my-cert <1>
 spec:
   selector:
     app: MyApp
@@ -73,9 +73,9 @@ $ oc describe secret my-cert
 Name:         my-cert
 Namespace:    openshift-console
 Labels:       <none>
-Annotations:  service.alpha.openshift.io/expiry: 2023-03-08T23:22:40Z
-              service.alpha.openshift.io/originating-service-name: my-service
-              service.alpha.openshift.io/originating-service-uid: 640f0ec3-afc2-4380-bf31-a8c784846a11
+Annotations:  service.beta.openshift.io/expiry: 2023-03-08T23:22:40Z
+              service.beta.openshift.io/originating-service-name: my-service
+              service.beta.openshift.io/originating-service-uid: 640f0ec3-afc2-4380-bf31-a8c784846a11
               service.beta.openshift.io/expiry: 2023-03-08T23:22:40Z
 
 Type:  kubernetes.io/tls
@@ -117,7 +117,7 @@ The certificate will be good for the internal service DNS name,
 +
 The certificate/key pair is automatically replaced when it gets
 close to expiration. View the expiration date in the
-`service.alpha.openshift.io/expiry` annotation on the secret, which is in
+`service.beta.openshift.io/expiry` annotation on the secret, which is in
 RFC3339 format.
 +
 [NOTE]

modules/nodes-pods-secrets-troubleshooting.adoc

@@ -6,7 +6,7 @@
 = Troubleshooting secrets
 
 If a service certificate generation fails with (service's
-`service.alpha.openshift.io/serving-cert-generation-error` annotation
+`service.beta.openshift.io/serving-cert-generation-error` annotation
 contains):
 
 [source,terminal]
@@ -17,8 +17,8 @@ secret/ssl-key references serviceUID 62ad25ca-d703-11e6-9d6f-0e9c0057b608, which
 The service that generated the certificate no longer exists, or has a different
 `serviceUID`. You must force certificates regeneration by removing the old
 secret, and clearing the following annotations on the service
-`service.alpha.openshift.io/serving-cert-generation-error`,
-`service.alpha.openshift.io/serving-cert-generation-error-num`:
+`service.beta.openshift.io/serving-cert-generation-error`,
+`service.beta.openshift.io/serving-cert-generation-error-num`:
 
 . Delete the secret:
 +
@@ -31,12 +31,12 @@ $ oc delete secret <secret_name>
 +
 [source,terminal]
 ----
-$ oc annotate service <service_name> service.alpha.openshift.io/serving-cert-generation-error-
+$ oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-
 ----
 +
 [source,terminal]
 ----
-$ oc annotate service <service_name> service.alpha.openshift.io/serving-cert-generation-error-num-
+$ oc annotate service <service_name> service.beta.openshift.io/serving-cert-generation-error-num-
 ----
 
 [NOTE]