Details
-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
Hypershift Sprint 241, Hypershift Sprint 242, Hypershift Sprint 243, Hypershift Sprint 244, Hypershift Sprint 245, Hypershift Sprint 246, Hypershift Sprint 247
-
0
-
0
-
0
Description
User Story:
When changing platform fields e.g. aws instance type we trigger a rolling upgrade, however nothing is signalled in the NodePool state which result in bad UX.
NodePools should signal rolling upgrade because of platform changes.
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.
Attachments
Issue Links
- relates to
-
OCPBUGS-18127 Changes to NodePool .spec.platfrom doesn't trigger a rolling upgrade
-
- Closed
-
- links to
- mentioned on
