Summary:

• It was previously found, that Autoscaling controller doesn't watch related resources correctly, which will prevent the controller to correctly react to their changes, which might result in the aodh pods not being configured as required. There is a fix already proposed in the following commit https://github.com/openstack-k8s-operators/telemetry-operator/commit/38ef2755eb0dd5de4f60e345d268716c8934964a . But a proper investigation of the current (pre-fix) behavior of the controller is needed, so that it can be verified, that the fix fixes all the issues.

Goal:

• See how the autoscaling controller reacts to changes to:
  • CA certificate secret
  • Aodh TLS secrets
  • Aodh config secrets
  • Aodh password in osp-secret
  • topology CR configured in the tepologyRef
• Document the incorrect behaviors

TimeBox:

• Less than a day once a environment is available

Deliverables/Outcomes:

• A comment specifying what's wrong.