-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.14
-
None
-
Moderate
-
No
-
3
-
False
-
Description of problem:
The servicemonitor named keda-metrics-apiserver is configured with incorrect port information after the CMA operator upgraded from v2.10.1-267 to v2.11.2-322.
Version-Release number of selected component (if applicable):
2.11.2-322
How reproducible:
100%
Steps to Reproduce:
1. Upgrade operator from v2.10.1-267 to latest version. 2. Check if keda-metrics-apiserver shows in available targets 3.
Actual results:
The target associated with keda-metrics-apiserver service went missing.
Expected results:
The target keda-metrics-apiserver should be available.
Additional info:
Ports configured in service "keda-metrics-apiserver" ========== ports: - name: https port: 443 protocol: TCP targetPort: 6443 - name: metrics port: 8080 protocol: TCP targetPort: 8080 ========== YAML spec of servicemonitor "keda-metrics-apiserver" ========== spec: endpoints: - interval: 60s port: http namespaceSelector: any: false selector: matchLabels: app.kubernetes.io/name: keda-metrics-apiserver ========== - Tried deleting "keda-metrics-apiserver" servicemonitor and it doesn't help. - The issue is not observed when the operator is deployed from the scratch.