-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
5
-
False
-
-
False
-
-
-
Installer Sprint 260, Installer Sprint 261
Currently the oc node-image create command looks for the kube-system/cluster-config-v1 resource to infer some of the required elements for generating the ISO.
The main issue is that the kube-system-cluster-config-v1 resource may be stale, since it contains information used when the cluster was installed, and that may have changed during the lifetime of the cluster.
tech note about the replacement
| Field | Source |
|---|---|
| APIDNSName | oc get infrastructure cluster -o=jsonpath='
{.status.apiServerURL}
' |
| ImageDigestSource | oc get imagedigestmirrorsets image-digest-mirror -o=jsonpath='
{.spec.imageDigestMirrors}
' |
| ImageContentSources | oc get imagecontentsourcepolicy |
| ClusterName | Derived from APIDNSName (api.<cluster name>.<base domain>) |
| SSHKey | oc get machineconfig 99-worker-ssh -o jsonpath='
{.spec.config.passwd.users[0].sshAuthorizedKeys}
' |
| FIPS | oc get machineconfig 99-worker-ssh -o jsonpath='
{.spec.fips}
' |
(see also zabitter comment in https://issues.redhat.com/browse/OCPBUGS-38802)
- links to
(2 links to)