Using service.beta.openshift.io as recommended method #1567
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ecommended method.
prakashsvmx
approved these changes
Apr 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective:
To upgrade our Operator versions in the different catalogs. Old annotations are not longer needed, and new annotations has to be used. OpenShift v4 vs OpenShift v3 annotations.
User Story:
service.beta.openshift.io/serving-cert-secret-nameis the current recommended method used from OpenShift v4 onwardsservice.alpha.openshift.io/serving-cert-secret-namewas the previous method used in OpenShift v3 which is no longer supported in the catalogs as per OpenShift 4.7 has reached its end of life #1565Links: