-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
4.12
-
Low
-
1
-
Sprint 229
-
1
-
Rejected
-
False
-
Description of problem:
After removed the replicas, it is empty in the ingresscontroller, while it isn't unchanged when oc get hpa. And the TARGETS is "1050m/1 (avg)"
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-08-31-101631
How reproducible:
follow the steps as "OCP-53957 - Negative test of ingress autoscaling" describes.
Steps to Reproduce:
1.just as "OCP-53952" describes, install the Custom Metrics Autoscaler by the web console. 2. scale the worker nodes to 20 % oc get hpa NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE keda-hpa-ingress-scaler IngressController/default 1050m/1 (avg) 1 20 20 8h % % oc get ingresscontroller/default -o yaml | grep replicas: replicas: 20 % 3. edit the default ingress-controller, delete the "relicas:" line under the spec % oc edit ingresscontroller/default ingresscontroller.operator.openshift.io/default edited % 4. % oc get ingresscontroller/default -o yaml | grep replicas: % 5. % oc get hpa NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE keda-hpa-ingress-scaler IngressController/default 1050m/1 (avg) 1 20 20 8h % 6. there are 2 router pods % oc -n openshift-ingress get pods NAME READY STATUS RESTARTS AGE router-default-58b9754d4d-g6666 1/1 Running 0 123m router-default-58b9754d4d-kvjm7 1/1 Running 0 123m %
Actual results:
relicas in hpa keda-hpa-ingress-scaler is different with that in the default ingresscontroller
Expected results:
relicas should be same between hpa keda-hpa-ingress-scaler and the default ingresscontroller, also not sure about the TARGETS "1050m/1 (avg)" in the output of oc get hpa
Additional info: