-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Allow blocking of payload registry
-
False
-
False
-
In Progress
-
Impediment
-
rhel-sst-container-tools
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Allow users to block the payload registry when mirror configuration is detected
Why is this important?
- Some customers in the disconnected environment want to block the upstream payload registry to comply with their security requirements. Allowing to block the payload registry when they have mirrors configured will allow them to be in compliance.
Scenarios
- ...
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>
- impacts account
-
RFE-2166 Be able to block quay.io in both connect and disconnected installs.
-
- Accepted
-
There are no Sub-Tasks for this issue.
