CORENET-5412: network: Gather OVN-Kubernetes CUDN CRs #486
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ormergi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ormergi
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@ormergi: This pull request references CORENET-5412 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:
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. |
| @@ -141,6 +141,8 @@ gather_scale_data | |||
|
|
|||
| if [[ "${NETWORK_TYPE}" == "ovnkubernetes" ]]; then | |||
| oc adm inspect ${log_collection_args} --dest-dir must-gather egressips.k8s.ovn.org | |||
| oc adm inspect ${log_collection_args} --dest-dir must-gather clusteruserdefinednetworks.k8s.ovn.org | |||
| oc adm inspect ${log_collection_args} --dest-dir must-gather userdefinednetworks.k8s.ovn.org --all-namespaces | |||
There was a problem hiding this comment.
remove udns since its tenant data and then rest lgtm
ormergi
force-pushed
the
gather-ovn-k-udn-crs
branch
from
7c16524 to
da9145c
Compare
ormergi
changed the title
|
@ormergi: This pull request references CORENET-5412 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:
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. |
The ClusterUserDefinedNetwork (CUDN) is cluster-scoped, installed by cluster-network-operator [1]. Creating CUDN CR result with a NetworkAttachmentDefinition (NAD) CR being created according to the CUDN CR 'spec.network', in each selected namespaces according to the CUDN CR 'spec.namespaceSelector'. Collect CUDN CRs. Having CUDN CRs collected enable troubleshooting OVN-Kubernetes user-defined networks in case of miss-configurations or env issues. The [1] https://github.com/openshift/cluster-network-operator Signed-off-by: Or Mergi <[email protected]>
ormergi
force-pushed
the
gather-ovn-k-udn-crs
branch
from
da9145c to
c3a1521
Compare
|
@ormergi: 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. |
The ClusterUserDefinedNetwork (CUDN) is cluster-scoped, installed by cluster-network-operator [1].
Creating CUDN CR result with a NetworkAttachmentDefinition (NAD) CR being created according to the CUDN CR 'spec.network', in each selected namespaces according to the CUDN CR 'spec.namespaceSelector'.
Collect CUDN CRs.
Having CUDN CRs collected enable troubleshooting OVN-Kubernetes user-defined networks in case of miss-configurations or env issues. The
[1] https://github.com/openshift/cluster-network-operator