Epic Goal

• Enable users to set a deadline for a revision to rollout before it reports a failed rollout

Why is this important?

• Progressing between ClusterExtension revisions can lead to a stuck rollout and users should be notified when the progression timeout had been exceeded to signal that manual action is required

Scenarios

1. A ClusterExtension is created by a persistent error (e.g. resource conflict, or probe failure) prevents it from being fully rolled out.
2. A ClusterExtension is being upgraded and a persistent error prevents it from being fully rolled out.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ClusterExtension API updated to take progression timeout as input
• API changes reviewed by API review team
• Once progression timeout is exceeded the ClusterExtension's Progression condition is set to False and not immediately re-enqueued for reconciliation

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>