This message was deleted.

unfortunately it looks like machine config properties are stored on the root of the kube resource, which means machine config properties that clash with reserved kube resource properties (like metadata) are invalid

@stocky-account-63046 Bummer. It looks like the actual

machine-config

values end up at

spec.template.spec

so in the final K8s resource definition it wouldn't conflict with the root level

metadata

field (sibling of

spec

)... are there any hooks available where I can map the name of the field last minute before it gets stored in the K8s resource so that it starts as

this.value.mdata

(to not conflict with

this.value.metadata

which seems to map to the root

metadata

field in the K8s resource to be) in

<my-extension-app>/pkg/<provider>/machine-config/<provider>.vue

but then ends up getting mapped to

metadata

before saved in K8s?

There could be hooks before the network request is sent, but server side afterwards where i think it's needed