Epic Goal

• Define the use cases, scope, and requirements for rolling upgrade lifecycle behavior for Klusterlet and Add-on agents
• Define a roadmap plan for execution on the requirements in a specified staged approach; e.g. Dev Preview -> Tech Preview -> GA
• Achieve agreement and consensus from stakeholders including consumers and add-on developers
• Proactively announce and establish expectations within the RHACM Program; including QE and CEE
• Open Cluster Management enhancement proposal submission and approval
• Add-on developers start early exploration of how these changes will impact their functionality
• Invesigate what happens when the hub control plane version and add-on versions are different

Non-goals

• Deliver a feature related to this in the 2.7/2.2 release for external usage

Why is this important?

• Given the scope and complexity of changes required in a rolling upgrade effort, we need to carefully establish requirements and plan
• We want to have all stakeholders across the ACM program prepared for these changes

Scenarios

1. Use Case Exploration

Acceptance Criteria

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

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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>