Bug bump cluster-capi-operator apirequests upper bound to 50
When deploying OCP with enabled CAPI, we got this error from the tests:
"Operator \"cluster-capi-operator\" produces more watch requests than expected: watchrequestcount=77, upperbound=72, ratio=1.0694444444444444""
Bumping the upperbound to 50 should solve this issue.
@@ -115,7 +115,7 @@ var _ = g.Describe("[sig-arch][Late]", func() {
"cloud-credential-operator": 146.0,
"cluster-autoscaler-operator": 132.0,
"cluster-baremetal-operator": 119.0,
- "cluster-capi-operator": 36.0,
+ "cluster-capi-operator": 50.0,
"cluster-image-registry-operator": 189.0,
"cluster-monitoring-operator": 124.0,
"cluster-node-tuning-operator": 115.0,
@@ -145,7 +145,7 @@ var _ = g.Describe("[sig-arch][Late]", func() {
"cloud-credential-operator": 99.0,
"cluster-autoscaler-operator": 100.0,
"cluster-baremetal-operator": 90.0,
- "cluster-capi-operator": 36.0,
+ "cluster-capi-operator": 50.0,
"cluster-image-registry-operator": 194.0,
"cluster-monitoring-operator": 99.0,
"cluster-node-tuning-operator": 92.0,
@@ -174,7 +174,7 @@ var _ = g.Describe("[sig-arch][Late]", func() {
"cloud-credential-operator": 48.0,
"cluster-autoscaler-operator": 54.0,
"cluster-baremetal-operator": 44.0,
- "cluster-capi-operator": 36.0,
+ "cluster-capi-operator": 50.0,
"cluster-image-registry-operator": 121.0,
"cluster-monitoring-operator": 56.0,
"cluster-node-tuning-operator": 112.0,
