Conversation
With OVN interconnect, an OVN instance is deployed on each node so, instead of deploying the pod on the master node, reuse the daemonset. Also, the entrypoint has to be modified to include well-known ovn-ic paths. Signed-off-by: Adrian Moreno <amorenoz@redhat.com>
Use openvswitch2.17 and OVN 23.09. Also, increase the memory limit as centos9's go compiler seems more memory hungry. Signed-off-by: Adrian Moreno <amorenoz@redhat.com>
|
with the new patches, installed ovsdb-mon.OVN_Northbound successfully with source ovsdb-mon-ovn-ic.source, and get the following result: [root@sdn-15 ovsdb-mon]# git log -1 --oneline source ovsdb-mon-ovn-ic.sourcenamespace/ovsdb-mon created NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE to remove daemonset created, do: kubectl delete -n ovsdb-mon ds ovsdb-mon oc get pod -n ovsdb-mon -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES |
|
Thanks @linup2011 for reporting and testing! |
Reported-by: @linup2011