We're pulling the metadata.json file off of the file system at the beginning of the install process and storing it in ClusterProvision.Spec.Metadata. But something is wrong – that field is empty. This appears to have been a problem for at least ~6mo, as it's the case for all the clusters currently on the hive-team cluster:

[efried@efried hive]$ oc get clusterprovision -A -o json | jq -r '.items[] | [.spec.metadata, .metadata.creationTimestamp]'
[
  {},
  "2022-04-22T13:35:49Z"
]
[
  {},
  "2022-03-17T01:22:36Z"
]
[
  {},
  "2022-09-09T17:34:32Z"
]
[
  {},
  "2022-06-30T16:45:10Z"
]
[
  {},
  "2022-08-30T20:23:29Z"
]

Exec'ing into a running provision pod, I can see the file in the right place and it's got stuff in it. So my hypothesis is that we're capturing it at the wrong time in the provisioning process.

[Later] Well, no, that isn't it. I did some debug logging and we're getting the right bytes. They're just not getting into the raw extension in the ClusterProvision. New hypothesis: this has something to do with raw extensions and how they muck up the CRD schema.