Update cert injection beta

[lance5890]

This PR implements a new data enhancement to...

Categories

• Bugfix
• Data Enhancement
• Feature
• Backporting
• Others (CI, Infrastructure, Documentation)

Sample Archive

• path/to/sample_data.json

Documentation

• path/to/documentation.md

Unit Tests

• path/to/file_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

Yes/No

References

https://issues.redhat.com/browse/???
https://access.redhat.com/solutions/???

• 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:

Summary by CodeRabbit

• Chores
  • Updated OpenShift service configuration annotations for improved platform compatibility.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e5a6e828-d17d-4d16-ad13-626711f87605

📥 Commits

Reviewing files that changed from the base of the PR and between 456de92 and 65ab5c9.

📒 Files selected for processing (1)

• manifests/06-service.yaml

---

📝 Walkthrough

Walkthrough

Updated a Service annotation in the OpenShift manifest from the alpha API version to the beta version. The serving certificate secret name remains unchanged. This is a straightforward annotation key update with no functional impact on the service configuration.

Changes

Cohort / File(s)	Summary
Service Annotation Update manifests/06-service.yaml	Updated Service annotation key from service.alpha.openshift.io/serving-cert-secret-name to service.beta.openshift.io/serving-cert-secret-name while preserving the secret name value.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hops through manifests with glee,
Alpha fades, beta's the key,
One small change, so clean and bright,
Annotations dance in the moonlight! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely a boilerplate template with placeholder values that don't match the actual changes. The categories, sample archive, documentation, unit tests, and references are all template text unrelated to the actual Service annotation update.	Replace template placeholders with actual content describing the cert injection annotation update. Update categories to reflect this is infrastructure/configuration change, not a data enhancement. Remove inapplicable sections.
Title check	❓ Inconclusive	The title 'Update cert injection beta' is vague and generic, using non-descriptive terms that don't clearly convey what specific change was made to the codebase.	Consider a more specific title like 'Update Service annotation from alpha to beta for cert injection' to clearly indicate the actual change being made.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[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 baiyangzhou 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

[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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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]

@lance5890: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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.

[lance5890]

/ok-to-test

[BaiyangZhou]

/test tls-scanner

[openshift-ci]

@lance5890: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.