-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump ovs-cni to 0.8.0 #267
Conversation
@qinqon don't forget to update |
The marker also fails with:
|
We gotta update the manifest, it has been changed on ovs-cni in k8snetworkplumbingwg/ovs-cni#80. |
176b3ed
to
ec1d76d
Compare
deploying and activaing OVS works fine.
We have to install ovs at nodes, why we didn't need it before ? the socket was created by container if does not exists ? |
ec1d76d
to
e09767b
Compare
1103511
to
8f8e702
Compare
That's what I commented. The difference is in the format of the socket parameter. |
Also the path, /run/openvswitch is no good. Now it has all it needs also I think we no longer need localbin since we are not using ovs-vsctl |
@@ -135,9 +135,7 @@ systemctl start NetworkManager | |||
## Open vSwitch | |||
|
|||
The operator allows administrator to deploy [OVS CNI plugin](https://github.com/kubevirt/ovs-cni/) | |||
simply by adding `ovs` attribute to `NetworkAddonsConfig`. Please note that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please say that openvswitch has to be running on the node.
To include the bridge reporting fix [1] [1] k8snetworkplumbingwg/ovs-cni#93 Signed-off-by: Quique Llorente <[email protected]>
8f8e702
to
0d6a24e
Compare
To include the bridge reporting fix [1]
[1] k8snetworkplumbingwg/ovs-cni#93
Signed-off-by: Quique Llorente [email protected]