XML

Word

Printable

Epic Name:
InternalReleaseImage certificate rotation
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:

75% To Do, 25% In Progress, 0% Done
Size:
L
Status Summary:
Hide

Jan 30, 2026 - Green

Analyzing existing MCS certificate rotation process and formulating plan to rotate IRI certificate. As a first step, we need to update IRI controller to recognize certificate changes and update master/worker ignitions. After that, we implement the IRI certificate rotation which will rely on first step as the mechanism to push out certificate changes.
Show
Jan 30, 2026 - Green Analyzing existing MCS certificate rotation process and formulating plan to rotate IRI certificate. As a first step, we need to update IRI controller to recognize certificate changes and update master/worker ignitions. After that, we implement the IRI certificate rotation which will rely on first step as the mechanism to push out certificate changes.

Epic Goal

Introduce a mechanism to allow the rotation of the TLS certificate used by the IRI registry

Why is this important?

The certificate generated by the installer when deploying a new cluster for the IRI registry doesn't not get rotated, and this is a requirement for the security concerns.

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>

links to