-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0
-
No
-
Hypershift Sprint 241
-
1
-
Rejected
-
False
-
Description of problem:
Changes to platform fields e.g. aws instance type doesn't trigger a rolling upgrade
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a hostedCluster with nodepool on AWS 2. Change the instance type field on the nodepool spec.platfrom.aws
Actual results:
Machines are not restarted and the instance type didn't change
Expected results:
Machines are recreated with the new instance type
Additional info:
This is a result of the recent changes to CAPI which introduced in-place propagation to labels and annotations Soultion: MachineTemplate name should not be constant and should change with each spec change, so that spec.infraRef in the MachineDeployment is updated and a rolling upgrade is triggered.
- is related to
-
HOSTEDCP-1133 NodePools should signal rolling upgrade because of platform changes
- Closed
- links to
-
RHEA-2023:5006 rpm
- mentioned on
(1 mentioned on)