Epic Goal

Operator sample(s) using ENV VAR for container images to align with the recommendations from the best practice section. 

Why is this important?

• We want to start evangelizing not hardcoded Operator/Operand container image(s) in the project in Go, Ansible, and Helm.
• Easier to manage Operator/Operand container image(s).
• Easier to pin image tags to digests in prod environment use cases.
• Easier to construct `relatedImages` fields for OLM API so the OLM can mirror all required images so the Operator can be running successfully in an air-gap environment. 

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

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>