openshift-docs
openshift-docs copied to clipboard
[WIP] OSDOCS-11920: Added OSD GCP Architecture models page.
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
@AedinC: This pull request references OSDOCS-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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.
🤖 Tue Nov 26 15:05:00 - Prow CI generated the docs preview:
https://83930--ocpdocs-pr.netlify.app/openshift-dedicated/latest/architecture/osd-architecture-models-gcp.html https://83930--ocpdocs-pr.netlify.app/openshift-dedicated/latest/osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.html
@AedinC: This pull request references OSDOCS-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams are placeholders. There is currently a backlog of tasks for the Graphics team to process. This document is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11). I also plan to reuse the PSC architecture overview module from OSDOCS-9401 in this doc. I will not be able to add this until after the latter is published (again scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11). I also plan to reuse the PSC architecture overview module from OSDOCS-9401 in this doc. I will not be able to add this until after the latter is published (again scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [ ] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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.
Just a couple of comments: I do wonder if we could reduce the size of the titles in the TOC? Maybe fine, and will have to stick with what is currently shown.
/label peer-review-done /remove-label peer-review-in-progress /lgtm
New changes are detected. LGTM label has been removed.
@AedinC: This pull request references OSDOCS-11920 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.18.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [x] Peer reviewer has approved this change.
SME review:
- [ ] SME has approved this change.
Additional information:
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.
Just a couple of comments: I do wonder if we could reduce the size of the titles in the TOC? Maybe fine, and will have to stick with what is currently shown.
Yeah agree it could look better! Think the inclusion of the PSC module has messed things up a bit. I will have a play around today to see if I can improve things-thanks!
On the architecture models page, can we update the following NOTE with what we have in the OCM UI. This is to highlight the customer benefits when using PSC - "Red Hat recommends using Private Service Connect when deploying a Private OpenShift Dedicated cluster on Google Cloud. Private Service Connect ensures there is a secured, private connectivity between Red Hat infrastructure, Site Reliability Engineering (SRE) and private OpenShift clusters."
Red Hat recommends the use of Private Service Connect-based architecture when deploying private OpenShift Dedicated clusters on GCP.
In Private OpenShift Dedicated on Google Cloud Platform (GCP) without Private Service Connect (PSC) architecture model sub-topic, can we add the same recommendation as above? This is to nudge customers to use PSC when deploying private clusters.
"Red Hat recommends using Private Service Connect when deploying a Private OpenShift Dedicated cluster on Google Cloud. Private Service Connect ensures there is a secured, private connectivity between Red Hat infrastructure, Site Reliability Engineering (SRE) and private OpenShift clusters."
Other than the above two comments, Architecture models page looks good.
@AedinC: This pull request references OSDOCS-11920 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.19.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
Note to reviewers: The diagrams added here are placeholders and are not official diagrams that have been created by the Diagrams team. There is currently a backlog of tasks for this team to process. This guide is not as high priority as the PSC guide, and updates to existing OSD-GCP documentation. As such, the diagrams are not likely to be ready until after feature release date (scheduled for 11/11).
QE review:
- [ ] QE has approved this change.
Peer review:
- [x] Peer reviewer has approved this change.
SME review:
- [x] SME has approved this change.
Additional information:
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-11920 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.19.0" version, but no target version was set.
In response to this:
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11920
Link to docs preview: Architecture models
QE review: No QE approval needed for this change.
Peer review:
- [x] Peer reviewer has approved this change.
SME review:
- [x] SME has approved this change.
Additional information:
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: all tests passed!
Full PR test history. Your PR dashboard.
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.
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
@EricPonvelle: new pull request created: #85492
In response to this:
/cherrypick enterprise-4.17
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.
@EricPonvelle: new pull request created: #85493
In response to this:
/cherrypick enterprise-4.18
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.