Description of problem:
oc patch the ingress-controller with spec.tuningOptions.healthCheckInterval 3d, but no new router pods are created, so the env ROUTER_BACKEND_CHECK_INTERVAL under router pods isn't changed.

OpenShift release version:
4.11.0-0.nightly-2022-05-25-193227

Cluster Platform:


How reproducible:
% oc -n openshift-ingress-operator patch ingresscontroller/default --type=merge -p '{"spec":{"tuningOptions": {"healthCheckInterval": "2d"}}}'

Steps to Reproduce (in detail):
1.
% oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-05-25-193227   True        False         8h      Cluster version is 4.11.0-0.nightly-2022-05-25-193227
% 

2. 
% oc -n openshift-ingress-operator get ingresscontroller/internalapps -o yaml | grep -A1 tuningOptions
  tuningOptions:
    healthCheckInterval: 1s
% 

3. get router pod before the patching
% oc -n openshift-ingress get pods | grep router-internalapps                                         
router-internalapps-76f489b5ff-fznk9   1/1     Running   0          3m33s
router-internalapps-76f489b5ff-htmvf   1/1     Running   0          3m33s
% 

4.patch ingresscontroller/internalapps with healthCheckInterval 3d
% oc -n openshift-ingress-operator patch ingresscontroller/internalapps --type=merge -p '{"spec":{"tuningOptions": {"healthCheckInterval": "3d"}}}'
ingresscontroller.operator.openshift.io/internalapps patched
%

5.
% oc -n openshift-ingress-operator get ingresscontroller/internalapps -o yaml | grep -A1 tuningOptions
  tuningOptions:
    healthCheckInterval: 3d
%

6. get router pod after the patching, no new router pods are created
% oc -n openshift-ingress get pods | grep router-internalapps
router-internalapps-76f489b5ff-fznk9   1/1     Running   0          31m
router-internalapps-76f489b5ff-htmvf   1/1     Running   0          31m
%

7. check env ROUTER_BACKEND_CHECK_INTERVAL in a router pod
% oc -n openshift-ingress rsh router-internalapps-76f489b5ff-fznk9
sh-4.4$ env | grep ROUTER_BACKEND_CHECK_INTERVAL
ROUTER_BACKEND_CHECK_INTERVAL=1s
sh-4.4$

Actual results:
no new router pods are created

Expected results:
new router pods with ROUTER_BACKEND_CHECK_INTERVAL=3d are created after the patching

Impact of the problem:


Additional info:



** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.