Shoud we automate the ignition creation on openshift cluster

[yalzhang]

In OpenShift, after installing the operator, we need to create a secret that wraps the ignition file:
https://github.com/trusted-execution-clusters/operator/blob/azure-demo/demo-azure/install-demo.sh#L44

This ignition file also embeds another ignition file from the current OpenShift cluster, which is served by an external web server:
https://github.com/trusted-execution-clusters/operator/blob/azure-demo/demo-azure/demo-ignition.json#L9

The cluster ignition is retrieved using:

oc get secret worker-user-data -n openshift-machine-api \
  -o jsonpath='{.data.userData}' | base64 --decode > worker.ign

Will all these steps be automated and handled by the operator?

[alicefr]

@yalzhang I think this needs to be done by something external because our operator doesn't know the rest of the ignition files. It just serves the clevis pin configuration. Maybe the right place is the MCO for this.