Epic Goal

• Customers require that we support "STS" mode credentials for Observability.
•  

Why is this important?

• Currently, the Observability plugin requires static IAM credentials (i.e. from an IAM User, not a Role). IAM Users and static credentials are not permitted in many customer environments.
• ROSA is a target for many customers. We need RHACM Observability to support ROSA first class.

Scenarios

1. Enhanced RHACM Observability to support "STS" mode credentials (i.e. IAM Role credentials).
2. Support RH ODF.
3. PREVENT the removal of annotations during CRD changes.
   1. Annotated SAs: "observability-thanos-store-shard", "observability-thanos-compact", "observability-thanos-receive" , "observability-thanos-receive-controller" and Thanos-rule 

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Ensure ACM QE we are tested fully working and functional with ACM + Multicluster Observability on ROSA using STS and RHODF storage.

Dependencies (internal and external)

1. ROSA + STS credentials

Previous Work (Optional):

1. …

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>