Fix NetworkEvents with upstream ovnk#2461
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2461 +/- ##
==========================================
+ Coverage 72.21% 72.53% +0.32%
==========================================
Files 104 104
Lines 10624 10629 +5
==========================================
+ Hits 7672 7710 +38
+ Misses 2477 2444 -33
Partials 475 475
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
b645afd to
c4abb6a
Compare
|
@jotak: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Description
When deploying upstream ovnk (on kind),
/var/run/ovn-icdoes not exist on host. The required sock can be found in/var/run/openvswitch.This fix introduces a Openshift/Non-Openshift condition, and also adds the env
OVN_OBSERV_HOST_MOUNT_PATHso that the host path can be overridden if necessary (as a last resort fallback; ideally, all use cases should be wired in code)Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.