When upgrading 4.12 cluster by using 4.13 oc, it returns the warning unknown field "spec.desiredUpdate.architecture"

# oc adm upgrade --to-image=registry.ci.openshift.org/ocp/release@sha256:8c5d10fcae776c33c11e126724a7ba78376acb82174f1dd1bc7f077105e43d4f --allow-explicit-upgrade 
warning: The requested upgrade image is not one of the available updates.You have used --allow-explicit-upgrade for the update to proceed anyway
Warning: unknown field "spec.desiredUpdate.architecture"
Requested update to release image registry.ci.openshift.org/ocp/release@sha256:8c5d10fcae776c33c11e126724a7ba78376acb82174f1dd1bc7f077105e43d4f

# oc get clusterversion/version -ojson | jq .spec
{
  "clusterID": "939e26d0-0a9f-4550-9253-c708daf40c06",
  "desiredUpdate": {
    "force": false,
    "image": "registry.ci.openshift.org/ocp/release@sha256:8c5d10fcae776c33c11e126724a7ba78376acb82174f1dd1bc7f077105e43d4f",
    "version": ""
  }
}

It doesn’t make much sense to me to set architecture when we don’t use option –to-multi-arch

 

# oc version
Client Version: 4.13.0-ec.3
Kustomize Version: v4.5.7
Server Version: 4.12.0-0.nightly-2023-03-03-043014
Kubernetes Version: v1.25.4+18eadca
 

2/2
 

1. Install a 4.12 cluster
2. Install a 4.13 oc
3. Upgrade 4.12 cluster using 4.13 oc

4.13 oc tries to set cv.spec.desiredUpdate.architecture on a 4.12 cluster which results in a warning to user
 

Oc doesn’t set cv.spec.desiredUpdate.architecture when option –to-multi-arch is not used