-
Story
-
Resolution: Done
-
Normal
-
None
-
None
The machine config node functionality should fully support custom machine config pools. Investigation from MCO-1299 highlights that custom MCPs are not supported. This story will be done when the following is complete:
- Custom pools should be reflected in the “POOLNAME” column when a user runs
$ oc get machineconfignode
- Users should be able to check the status of a specific, custom MCP using
$ oc get machineconfignodes $(oc get machineconfignodes -o json | jq -r '.items[]|select(.spec.pool.name=="<pool_name>")|.metadata.name')
- MCNs (as seen when running oc describe machineconfignode/<node-name>) should reflect the custom pools a node is a part of under Spec.Pool.Name
- blocks
-
OCPBUGS-52302 Desired config version in MCN is being set in status before spec
-
- MODIFIED
-
-
OCPBUGS-38869 MCN desired config is not updated when we use OCL
-
- Closed
-
- is depended on by
-
MCO-1520 [API 5/6] Create 5 tests in openshift/origin for GA readiness signal
-
- Closed
-
- is related to
-
OCPBUGS-52656 Pinnedimageset fails when there is a custom MCP
-
- Closed
-
- links to
(2 links to)