Deployment of a 4.13.z SNO spoke from a hub cluster with ACM 2.8 fails. The
failure is caused by warning messages generated by the recommended siteconfig
for pre-caching as described here: https://docs.openshift.com/container-platform/4.13/scalability_and_performance/ztp_far_edge/ztp-precaching-tool.html#ztp-pre-caching-config-con_pre-caching

Specifically the ignitionConfigOverride key/value

The recommended pre-caching configuration likely needs to be updated to correct this issue, and least for OCP 4.13+

OCP 4.13.z (hub and spoke)
ACM 2.8 (hub)

Always

1. Depoloy 4.13.z hub cluster with ACM 2.8
2. Attempt to deploy spoke with OCP 4.13.z with the DU profile, including the
   recommended configuration for pre-caching as linked above. 
3.

Spoke deployment fails and generates the following warning messages on the console (orange text). Image also linked in a comment below

Spoke deployment succeeds

hub$ cat <<EOF | kubectl create -f -
> apiVersion: v1
> kind: ConfigMap
> metadata:
>   name: my-assisted-service-config
>   namespace: multicluster-engine
> data:
>   ALLOW_CONVERGED_FLOW: "false"
> EOF
configmap/my-assisted-service-config created

hub$ oc annotate --overwrite AgentServiceConfig agent unsupported.agent-install.openshift.io/assisted-service-configmap=my-assisted-service-config