Description of problem:

changes/modification/update in egressrouter CR does not reflect in the egressrouter pod.

How reproducible: Always

Steps to Reproduce:

1. Create a egressrouter

2.
   a)  Make some changes in the redirectrules of egressrouter CR yaml file and `oc apply -f <file>` (I tried appending one more redirectrule)
   Note: For some reason, directly editing the egressrouterCR wipes of the previous redirectrules data and only shows the updated/changed config of redirectrule.

3. Once the above changes are applied, the egressrouter pod need to be manually restarted in order to get the new configurations.

Actual results:

• Any update in egressrouterCR does not reflect in the egressrouter pod unless restarted.
• `connection refused` error is encountered until the pod is restarted. (since i tried adding new redirectrule)

Expected results:

• Any update in the egressrouterCR should trigger an automatic restart of the egressrouter pod (to reflect the new changes from egressrouter CR).

Affected Platforms:
Is it an customer issue / SD

1. internal RedHat testing failure