-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18.z
-
None
-
None
-
Hypershift Sprint 263
-
1
-
False
-
Description of problem:
Currently both the nodepool controller and capi controller set the updatingConfig condition on nodepool upgrades. We should only use one to set the condition to avoid constant switching between conditions and to ensure the logic used for setting this condition is the same.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
CAPI and Nodepool controller set a different status because their logic is not consistent.
Expected results:
CAPI and Nodepool controller set the same status because their logic is not cosolidated.
Additional info: