Hello,
Not sure this is the right place to open this report...
We're using the egressRouter on our OKD 4.20 cluster that is using the CNO.
If we create an egressRouter resource, the CNI plugin pod is created, with the proper routes and nftables rules.
However, if we modify the spec of the egressRouter after it's been created, the changes are not reflected in the pod and we have to manually rollout the pod in order for the configuration changes to take effect.
I see in the CNO logs that it's reconciling the egressRouter resource every five minutes but I'm a bit puzzled by the fact the configuration changes are not reflected. Is this the intended behavior ? It would probably be logical to reload/update the nftables rules and routes on config change.
Please advise.
Best regards,
Hello,
Not sure this is the right place to open this report...
We're using the egressRouter on our OKD 4.20 cluster that is using the CNO.
If we create an egressRouter resource, the CNI plugin pod is created, with the proper routes and nftables rules.
However, if we modify the spec of the egressRouter after it's been created, the changes are not reflected in the pod and we have to manually rollout the pod in order for the configuration changes to take effect.
I see in the CNO logs that it's reconciling the egressRouter resource every five minutes but I'm a bit puzzled by the fact the configuration changes are not reflected. Is this the intended behavior ? It would probably be logical to reload/update the nftables rules and routes on config change.
Please advise.
Best regards,