You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consume openvswitch-ipsec systemd service for OVN IPsec deployment
The ovn-ipsec-host daemonset pod currently spins up ovs-monitor-ipsec process
to configure IPsec connections with the peer nodes. This would make ipsec
connections to be established for the existing nodes a bit later after kubelet
is started at the time node/service restart scenario, but by the time workloads
are scheduled on the node started hitting traffic drops because of
unavailability of IPsec connections between nodes. This makes IPsec jobs in CI
so unstable and monitor jobs always failing during IPsec upgrade.
The FDP story (https://issues.redhat.com/browse/FDP-1051) gets openvswitch-ipsec
systemd service (runs ovs-monitor-ipsec) with required configurable parameters,
It's available with OVS 3.5 version. So this commit does the following.
1. Stop spawning ovs-monitor-ipsec as foreground process in the ovn-ipsec
container, Instead setup required IPsec configuration parameters in the
/etc/sysconfig/openvswitch file, enable and start the openvswitch-ipsec
service on the host. This is done at the of when ovn-ipsec-host pod is
coming up for the first time, for the pod restart scenarios, it just
checks openvswitch-ipsec service is running on the host, otherwise exit
from the container with error.
2. Keep running an ovn-ipsec container and redirects /var/log/openvswitch/ovs-monitor-ipsec.log
to the ovn-ipsec container's stdout console.
3. There is no necessity of having ovn-ipsec-clean container anymore with
openvswitch-ipsec service as it's going to handle OVN IPsec states
appropriately.
4. During the OCP upgrade, the new ipsec os extension takes while to deploy
with openvswitch3.5-ipsec package, so by the time ovn-ipsec-host daemonset
is rendered, We need to handle that scenario by running ovs-monitor-ipsec
in the container. so this commit is also considering the transition phase
of the process that is moving from container to host.
5. The ovn-keys init container configures ovs with IPsec certificate paths,
so the container uses same host directory path to store and configure ovs
with certificates because the ovs-monitor-ipsec process is running on the
host now.
Signed-off-by: Periyasamy Palanisamy <[email protected]>
0 commit comments