-
Epic
-
Resolution: Won't Do
-
Critical
-
None
-
None
-
None
Epic Goal
- Make publish (how to publish the user-facing endpoints of your cluster) parameter to other operators.
Why is this important?
- The image registry operator creates and uses an Azure storage account, and it needs to know if this account is allowed to have a public endpoint or not. A public endpoint in a private environment is against Azure security recommendations and raises a security alert.
Scenarios
- As a user, I want all created resources to respect publish parameter, even those created by the operators, so that Azure doesn't alert about endpoints security problems.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
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 - Downstream documentation merged: <link to meaningful PR>