-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhos-18.0.6, rhos-18.0.7, rhos-18.0.8, rhos-18.0.9, rhos-18.0.15, rhos-18.0.14 FR 4, rhos-18.0.13, rhos-18.0.12, rhos-18.0.11, rhos-18.0.10 FR 3
-
None
-
0
-
False
-
-
False
-
?
-
rhos-conplat-observability
-
None
-
-
-
-
Bug Delivery Tracker
-
1
-
Low
To Reproduce
The mysqld-exporter and kube-state-metrics although managed by the ceilometer exporter are treated mostly as separate services. There are some plans to make this more apparent in the CR structure and in controller code in RHOSO 19. Because of that, they use their own serviceLabels and they should be able to use different topologies than ceilometer itself.
Expected behavior
- Different topologies are configurable for mysqld-exporter, kube-state-metrics and ceilometer.
- When a topology is being used for mysqld-exporter or kube-state-metrics, the correct label selector is used in <pod_name>.spec.topologySpreadConstraints.labelSelector.
Bug impact
- Topologies can't be used with mysqld-exporter and kube-state-metrics