OSDOCS-8515: Documented the 4.15 Welcome page #70120
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@dfitzmau: This pull request references OSDOCS-8515 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.16.0" version, but no target version was set. In 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. |
|
@dfitzmau: This pull request references OSDOCS-8515 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.16.0" version, but no target version was set. In 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 09 11:07:40 - Prow CI generated the docs preview: https://70120--ocpdocs-pr.netlify.app |
|
@dfitzmau: This pull request references OSDOCS-8515 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.16.0" version, but no target version was set. In 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
size/M
dfitzmau
force-pushed
the
OSDOCS-8515
branch
3 times, most recently
from
73bebf1 to
c291c31
Compare
|
@dfitzmau: This pull request references OSDOCS-8515 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.16.0" version, but no target version was set. In 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. |
dfitzmau
force-pushed
the
OSDOCS-8515
branch
5 times, most recently
from
94829ce to
f8d6bc7
Compare
|
@dfitzmau: This pull request references OSDOCS-8515 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.16.0" version, but no target version was set. In 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. |
|
/label peer-review-needed Note to reviewers. Most feedback was pooled from the Google Doc. Any items in the GDoc coloured in Orange might or might not make the 4.15 release. A new PR could be created closer to that time by component writers to update the Welcome page. |
|
/label peer-review-needed Reviewer: See the Description section for the Google doc. |
openshift-ci
bot
added
the
peer-review-needed
mburke5678
added
the
peer-review-in-progress
welcome/index.adoc
Outdated
| Use the Cluster Version Operator (CVO) to upgrade your {product-title} cluster. If an update is available from the OpenShift Update Service (OSUS), you apply that cluster update from the {product-title} xref:../updating/updating_a_cluster/updating-cluster-web-console.adoc#updating-cluster-web-console[web console] or the xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[OpenShift CLI] (`oc`). | ||
|
|
||
| - **xref:../updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update-osus.adoc#update-service-overview_updating-restricted-network-cluster-osus[Using the OpenShift Update Service in a disconnected environment]**: Learn about installing and managing a local OpenShift Update Service for recommending {product-title} updates in disconnected environments. | ||
| - **xref:../updating/updating_a_cluster/updating_disconnected_cluster/index.html[Using the OpenShift Update Service in a disconnected environment]**: Learn about installing and managing a local OpenShift Update Service for recommending {product-title} updates in disconnected environments. |
There was a problem hiding this comment.
Should this one also use the You can structure like most/all of the other links here?
| - **xref:../updating/updating_a_cluster/updating_disconnected_cluster/index.html[Using the OpenShift Update Service in a disconnected environment]**: Learn about installing and managing a local OpenShift Update Service for recommending {product-title} updates in disconnected environments. | |
| - **xref:../updating/updating_a_cluster/updating_disconnected_cluster/index.html[Using the OpenShift Update Service in a disconnected environment]**: You can use the OpenShift Update Service for recommending {product-title} updates in disconnected environments. |
mburke5678
added
peer-review-done
dfitzmau
force-pushed
the
OSDOCS-8515
branch
2 times, most recently
from
9072cd7 to
0b78793
Compare
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
jeana-redhat
added
the
merge-review-in-progress
welcome/index.adoc
Outdated
| endif::[] | ||
|
|
||
| // Need to provide a link closer to 4.15 GA | ||
| - **Software Supply Chain Enhancements**: The PipelineRun *Details* view in the *Developer* or *Administrator* perspective of the web console provides an enhanced visual representation of PipelineRuns within a Project. Learn about the Software Supply Chain enhancements and how to deploy them. |
There was a problem hiding this comment.
- "PipelineRun" looks like an object of some type. Probably needs backticks and some noun to follow it.
- Should also double-check "Software Supply Chain" capitalization. Is it a component, or should that just be normal lower case use?
| - **Software Supply Chain Enhancements**: The PipelineRun *Details* view in the *Developer* or *Administrator* perspective of the web console provides an enhanced visual representation of PipelineRuns within a Project. Learn about the Software Supply Chain enhancements and how to deploy them. | |
| - **Software Supply Chain enhancements**: The `PipelineRun` *Details* view in the *Developer* or *Administrator* perspective of the web console provides an enhanced visual representation of `PipelineRun` objects within a project. Learn about the Software Supply Chain enhancements and how to deploy them. |
There was a problem hiding this comment.
There was a problem hiding this comment.
"Red Hat Trusted Software Supply Chain" then I guess? What a mouthful 😵
There was a problem hiding this comment.
Sorry, I also pinged Gaurav Trivedi on Slack to confirm 🖊️
There was a problem hiding this comment.
PR #70231 is planned for merging before the 4.15 GA. I'll create a subtask on my Welcome page Jira to comment in the link when the SSCS doc is published.
Jira subtask: https://issues.redhat.com/browse/OSDOCS-9616
There was a problem hiding this comment.
For "details page", see link.
openshift-ci
bot
removed
merge-review-in-progress
dfitzmau
force-pushed
the
OSDOCS-8515
branch
6 times, most recently
from
f16d119 to
8070f06
Compare
|
@dfitzmau I've reviewed the software supply chain security content and it reads well. That you for adding and updating it. |
|
@dfitzmau: 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/test-infra repository. I understand the commands that are listed here. |
|
/cherrypick enterprise-4.15 |
|
@jeana-redhat: new pull request created: #71425 In 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 kubernetes/test-infra repository. |
| @@ -84,32 +84,33 @@ Explore the following {product-title} installation tasks: | |||
|
|
|||
| - **xref:../installing/installing_azure_stack_hub/preparing-to-install-on-azure-stack-hub.adoc#preparing-to-install-on-azure-stack-hub[Install a cluster on Azure Stack Hub]**: On Microsoft Azure Stack Hub, you can install {product-title} on installer-provisioned infrastructure or user-provisioned infrastructure. | |||
|
|
|||
| - **xref:../installing/installing_gcp/preparing-to-install-on-gcp.adoc#preparing-to-install-on-gcp[Install a cluster on GCP]**: On Google Cloud Platform (GCP) you can install {product-title} on installer-provisioned infrastructure or user-provisioned infrastructure. | |||
| - **xref:../installing/installing_on_prem_assisted/installing-on-prem-assisted.html#using-the-assisted-installer_installing-on-prem-assisted[Installing {product-title} with the Assisted Installer]**: The Assisted Installer is an installation solution that is provided on the Red Hat {hybrid-console}. The Assisted Installer supports installing an {product-title} cluster on many platforms, but with a focus on bare metal, Nutanix, and {vmw-full} infrastructures. | |||
Version(s):
4.15
Issue:
Link to docs preview:
Welcome page
QE review:
Additional information: