Ghost Node Pool in UI if cluster created outside of UI

[inichols]

If you create a cluster.provisioning.cattle.io object for an elemental cluster, it will work as expected, but UI then shows the node pool twice.

Checked to see if there was a duplicate machinedeployment, but only saw one there:

kubectl get machinedeployments.cluster.x-k8s.io -n fleet-default
NAME         CLUSTER   REPLICAS   READY   UPDATED   UNAVAILABLE   PHASE     AGE     VERSION
test-pool1   test      1          1       1         0             Running   4m50s

This looks to be the same if you create it via TF. Unsure, but to be able to create an Elemental cluster via YAML or TF, you do need to precreate the machineinventoryselectortemplates.elemental.cattle.io as it isn't created via the cluster object but rather the UI creates it during the process of setup in the UI for the new cluster. Not sure if this has to deal with the reason two node pools appear.