Description of problem:

Everytime we restart ovnkube-node chains are flushed or rules in chains are flushed. Let's be smarter...

W0714 15:49:33.531277 13288 gateway_iptables.go:72] SURYA REINSERTING: OVN-KUBE-SNAT-MGMTPORT:-:nat:-:[-p TCP --dport 31248 -j RETURN]
W0714 15:49:33.554023 13288 gateway_iptables.go:72] SURYA REINSERTING: OVN-KUBE-NODEPORT:-:nat:-:[-p TCP -m addrtype --dst-type LOCAL --dport 31248 -j DNAT --to-destinat
ion 10.96.42.192:80]
W0714 15:49:33.579462 13288 gateway_iptables.go:72] SURYA REINSERTING: OVN-KUBE-ETP:-:nat:-:[-p TCP -m addrtype --dst-type LOCAL --dport 31248 -j DNAT --to-destination 1
69.254.169.3:31248]
W0714 15:49:33.600767 13288 gateway_iptables.go:72] SURYA REINSERTING: OVN-KUBE-SNAT-MGMTPORT:-:nat:-:[-p TCP --dport 31248 -j RETURN]
W0714 15:49:33.632875 13288 management-port_linux.go:234] SURYA CHAIN NOT FOUND OVN-KUBE-SNAT-MGMTPORT:-:false::<nil>::ovn-k8s-mp0::10.244.0.2:-:[-o ovn-k8s-mp0 -m comment --comment OVN SNAT to Management Port -j SNAT --to-source 10.244.0.2]
W0714 15:49:33.635952 13288 management-port_linux.go:312] missing management port nat rule in chain OVN-KUBE-SNAT-MGMTPORT, adding it

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: