OSDOCS-18115:Added info about OSD listing in Google Cloud console.#106124
OSDOCS-18115:Added info about OSD listing in Google Cloud console.#106124AedinC wants to merge 1 commit intoopenshift:mainfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@AedinC: This pull request references OSDOCS-18115 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
1 similar comment
|
@AedinC: This pull request references OSDOCS-18115 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/S
|
🤖 Fri Feb 06 16:24:06 - Prow CI generated the docs preview: https://106124--ocpdocs-pr.netlify.app/openshift-dedicated/latest/osd_planning/gcp-ccs.html |
| [role="_abstract"] | ||
| {product-title} clusters using a Customer Cloud Subscription (CCS) model on {gcp-first} must meet several prerequisites before they can be deployed. | ||
|
|
||
| As a {gcp-short} user, you can validate many of these requirements directly within the link:https://cloud.google.com/openshift[{gcp-short} console] prior to deployment. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'before' rather than 'prior to'. For more information, see RedHat.TermsErrors.
|
@AedinC: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@AedinC: This pull request references OSDOCS-18115 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@AedinC: This pull request references OSDOCS-18115 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@AedinC: This pull request references OSDOCS-18115 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@shreyansvm Can you please review? Note that the release note text has been trimmed down from the Google doc and simplified to adhere to our release note S&Gs. Thanks! |
|
Hi @AedinC : Thanks for drafting these changes with priority. Few comments: Comments on release note updates: "initiate cluster deployment without leaving the Google Cloud interface" ==> This is not accurate. It also contradicts with "Validate your Google Cloud configuration directly in the console before transitioning to a guided deployment flow in the Red Hat Hybrid Cloud Console". The later is correct i.e. users cannot initiate cluster deployment from within the Google Cloud interface. They will be redirected to the Red Hat Hybrid Cloud Console for cluster provisioning (and day-2 operations).
The 3rd bullet point you removed is more about the value of the transaction through the Google Cloud Marketplace. Not sure why we can't add this to the release notes. Is the issue with the end of the sentence which refers to spend and discounts?
Would it be okay to remove "using the Customer Cloud Subscriptions (CCS) model"?
Comments on Understanding Customer Cloud Subscriptions on Google Cloud
Here's the link directly to the OSD Prerequisite Check page within the Google Cloud console. This is not yet live to the public. https://console.cloud.google.com/redhat-openshift/verify
|
|
Thanks for the feedback @shreyansvm. We are not supposed to refer to pricing information in our documentation, but let me double check with the team to see if we can include that info. |
6 participants
Version(s):
4.21+
Issue:
OSDOCS-18115
Link to docs preview:
Understanding Customer Cloud Subscriptions on Google Cloud
Q1 2026
Peer review:
SME review:
QE review:
Additional information:
Note to reviewers: placeholder links are there until OpenShift listing goes live in Google Cloud console.