openshift
[WIP] OSDOCS-11411: Adding ROSA-compatible multi-arch scheduling content
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-11411
Link to docs preview:
- OCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html
- ROSA + HCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-multi-arch-cluster-managing.html
QE review:
- [ ] QE has approved this change
Additional information: Same content as https://github.com/openshift/openshift-docs/pull/83236 just a different approach with some wording rejiggered.
@laubai: This pull request references OSDOCS-11411 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-11411
Link to docs preview: TBD
QE review:
- [x] QE has approved this change
Additional information: Same content as https://github.com/openshift/openshift-docs/pull/83236 just a different approach with some wording rejiggered.
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.
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
🤖 Tue Nov 26 05:02:01 - Prow CI generated the docs preview:
https://83997--ocpdocs-pr.netlify.app/ https://83997--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html https://83997--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-multi-arch-cluster-managing.html
@laubai: This pull request references OSDOCS-11411 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-11411
Link to docs preview:
- OCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html
- ROSA + HCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-multi-arch-cluster-managing.html
QE review:
- [ ] QE has approved this change
Additional information: Same content as https://github.com/openshift/openshift-docs/pull/83236 just a different approach with some wording rejiggered.
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.
@laubai: This pull request references OSDOCS-11411 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-11411
Link to docs preview:
- OCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html
- ROSA with HCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-multi-arch-cluster-managing.html
- ROSA Classic docs: waiting on build
QE review:
- [ ] QE has approved this change
Additional information: Same content as https://github.com/openshift/openshift-docs/pull/83236 just a different approach with some wording rejiggered.
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.
@laubai: This pull request references OSDOCS-11411 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-11411
Link to docs preview:
- OCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html
- ROSA with HCP docs: https://83997--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-multi-arch-cluster-managing.html
- ROSA Classic docs: https://83997--ocpdocs-pr.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa-cluster-notifications (not included)
QE review:
- [ ] QE has approved this change
Additional information: Same content as https://github.com/openshift/openshift-docs/pull/83236 just a different approach with some wording rejiggered.
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.
Note for the peer reviewer that peer review, QE review, and merge review were carried out on the earlier PR, it just needed to be merged to a different branch :)
@laubai: 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.
@kcarmichael08: new pull request created: #85494
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.
@kcarmichael08: new pull request created: #85495
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.