openshift-docs
openshift-docs copied to clipboard
OSDOCS-9535: RN update for microarchitecture requirement change
Version(s): 4.13
Issue: https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview: https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
QE review:
- [x] QE has approved this change.
Additional information: This covers the RN update - a future PR will cover the rest of the doc update for 4.13+ :)
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue.
In response to this:
Version(s): 4.13
Issue: https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information: This covers the RN update - a future PR will cover the rest of the doc update for 4.13+ :)
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.
🤖 Fri May 17 14:51:42 - Prow CI generated the docs preview:
https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue.
In response to this:
Version(s): 4.13
Issue: https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview: https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
QE review:
- [ ] QE has approved this change.
Additional information: This covers the RN update - a future PR will cover the rest of the doc update for 4.13+ :)
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.
/lgtm
/cc
As bug OSDOCS-9535 said, if we do not set cpu architecture will cause upgrade fail, so shall we highlight the statement here?
As bug OSDOCS-9535 said, if we do not set cpu architecture will cause upgrade fail, so shall we highlight the statement here?
I will add that note to the actual upgrade documentation for 4.13+. This PR just covers the release note update :)
/lgtm
Thank you @obrown1205 for the updates
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue.
In response to this:
Version(s): 4.13
Issue: https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview: https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
QE review:
- [x] QE has approved this change.
Additional information: This covers the RN update - a future PR will cover the rest of the doc update for 4.13+ :)
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
/remove-label peer-review-needed /label peer-review-in-progress
/remove-label peer-review-in-progress /label peer-review-done
/label merge-review-needed
Does this PR need change management? Seems like it might but I just wanted to check
/lgtm
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue.
In response to this:
Version(s): 4.13
Issue: https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview: https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
QE review:
- [x] QE has approved this change.
Additional information: No change management required - confirmed
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 merge-review-needed
/label merge-review-in-progress
/remove-label merge-review-needed
/remove-label merge-review-in-progress
New changes are detected. LGTM label has been removed.
@obrown1205: 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.