XML

Word

Printable

Epic Name:
InternalReleaseImage registry credentials management
Activity Type:
Product / Portfolio Work
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Green
Epic Status:
In Progress
Feature Link:
OCPSTRAT-2251 - [GA] Agent Installer for OpenShift Virtualization - Day-1 and Day-2 add a new node w/o an external registry
Parent Link:
OCPSTRAT-2251[GA] Agent Installer for OpenShift Virtualization - Day-1 and Day-2 add a new node w/o an external registry
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Size:
M
Status Summary:
Hide

Jan 30, 2026 - Green

Began spike to research how image-registry currently handle credentials and possible options for IRI registry.
Show
Jan 30, 2026 - Green Began spike to research how image-registry currently handle credentials and possible options for IRI registry.

Epic Goal

Protect the IRI registry with proper credentials generated during the installation
Allow to rotate the credentials when required

Why is this important?

Currently the IRI registry is accessible r/w on port 22625 on every control plane node. This is mainly required to allow adding new nodes to the cluster. The registry access must be then fenced with a proper credentials

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

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>