openshift-docs
openshift-docs copied to clipboard
OSDOCS-9469: Documented the configure-ovs alternative
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [ ] SME has approved this change
- [ ] QE has approved this change.
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s):
Issue:
Link to docs preview:
QE review:
- [ ] QE 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.
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
QE review:
- [ ] QE 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.
🤖 Mon Jul 22 11:17:50 - Prow CI generated the docs preview: https://76548--ocpdocs-pr.netlify.app Complete list of updated preview URLs: artifacts/updated_preview_urls.txt
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
QE review:
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
QE review:
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
QE review:
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- [ ] SME has approved this change
- [ ] QE has approved this change.
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.
/jira-refresh
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [ ] SME has approved this change
- [ ] QE has approved this change.
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-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [x] SME has approved this change
- [ ] QE has approved this change.
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
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16+
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [x] SME has approved this change
- [ ] QE has approved this change.
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
@dfitzmau: This pull request references OSDOCS-9469 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead.
In response to this:
Version(s): 4.16+
Issue: OSDOCS-9469
Link to docs preview:
- About the Kubernetes NMState Operator
- Migrating to the OVN-Kubernetes network plugin
- Installing a user-provisioned cluster on bare metal
- Installing a user-provisioned bare metal cluster with network customizations
- Installing a user-provisioned bare metal cluster on a restricted network
- Setting up the environment for an OpenShift installation IPI
- Postinstallation configuration IPI
- Postinstall UPI
- DNS
- [x] SME has approved this change
- [x] QE has approved this change.
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
New changes are detected. LGTM label has been removed.
@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-sigs/prow repository. I understand the commands that are listed here.
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.16
@stevsmit: new pull request created: #79216
In response to this:
/cherry-pick 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.
@stevsmit: new pull request created: #79217
In response to this:
/cherry-pick enterprise-4.16
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.