update cert injection annotations to beta

[lance5890]

• the serving-cert-secret description can be found in https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/security_and_compliance/configuring-certificates#add-service-certificate_service-serving-certificate
• this is the change of beta version in service ca operator : openshift/service-ca-operator@9820fea#diff-81a43fd4d98d3cb6bac44c7a083efc4f5ad81887646dce6ea0c744dc786369b7
• this is kind of clean up:

apiVersion: v1
kind: Service
metadata:
  annotations:
    include.release.openshift.io/hypershift: "true"
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    service.alpha.openshift.io/serving-cert-secret-name: config-operator-serving-cert
    service.alpha.openshift.io/serving-cert-signed-by: openshift-service-serving-signer@1770865526
    service.beta.openshift.io/serving-cert-signed-by: openshift-service-serving-signer@1770865526

[coderabbitai]

Walkthrough

The config operator service manifest is updated to change a Kubernetes annotation key from the alpha API version to the beta API version for the serving certificate configuration. This is a direct mapping change with no other modifications.

Changes

Cohort / File(s)	Summary
Service Manifest Annotation Update manifests/0000_10_config-operator_02_service.yaml	Updates serving certificate annotation key from service.alpha.openshift.io/serving-cert-secret-name to service.beta.openshift.io/serving-cert-secret-name.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

Hi @lance5890. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lance5890
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment