Epic Goal
Deploying an Operator in OCP is made simple by accessing the Operator Hub in the console, browsing the operators, selecting and configuring the operator and clicking install. This epic is to extend that experience one step further, make the Operator install work nicely across multiple clusters using ACM APIs that can turn the Operator into an OperatorPolicy that can be deployed to many clusters using placement or work APIs.
Why is this important?
Managing a fleet of operators can be improved when ACM is available. ACM can help drive the operator deployment across many clusters and can use ACM's search and discovered policies to quickly identify where operator concerns are.
Scenarios
Deploy operators in a multicluster way instead of just to the local cluster when the user is logged into the ACM hub.
Be able to view deployed policies across the multicluster fleet. Identify cases where upgrades are available and other details that can be provided through ACM search and OperatorPolicy. This could be through linking to existing views for discovered policies.
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.