-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
As a result of the investigations in MCO-1542 and MCO-1682, updates to the MachineConfigNode (MCN) API object are needed. This task involves making the necessary changes decided on in the mentioned spikes.
Done when:
- MCN API has the following changes:
- MCN.Spec.ConfigImage
- Field similar to MCN.Spec.ConfigVersion to hold the node's `machineconfiguration.openshift.io/desiredImage` annotation value.
- MCN.Status.ConfigImage
- Field similar to MCN.Status.ConfigVersion to hold the node's `machineconfiguration.openshift.io/desiredImage` and `machineconfiguration.openshift.io/currentImage` annotation values.
- Add the following to the the `StateProgress` enum so that they can be used as condition types in MCN.Status.Conditions.
- Split `AppliedFilesAndOS` into `AppliedOSImage` and `AppliedFiles`.
- Note that "splitting" this condition might not be allowed. Rather we may need to simply add `AppliedOSImage` and `AppliedFiles` phases and phase out the use of `AppliedFilesAndOS`. This may require conversations with the API team.
- Add `ImagePulledFromRegistry`.
- Split `AppliedFilesAndOS` into `AppliedOSImage` and `AppliedFiles`.
- MCN.Spec.ConfigImage
- Note that this does not include merging the API. That work, including the work associated with socializing the API changes, should be tracked as part of
MCO-1856.
References:
- An example of a PR introducing new fields into an existing API tying back to a Feature Gate can be found here.
- depends on
-
MCO-1542 Finalize MCN statuses for status reporting GA
-
- Closed
-
-
MCO-1682 Investigate if MCN API updates are needed to represent OCL's current and desired image values
-
- Closed
-
- is cloned by
-
MCO-1856 [API 2/6 - Merge Work] Update API for Status Reporting needs
-
- Closed
-
- is depended on by
-
MCO-1740 [API 3/6] Version bump the API in client-go
-
- Closed
-
- is related to
-
OCPBUGS-43435 After OCL is enabled few phases in MCN are not updating as expected
-
- New
-
- links to