adamant-kite-43734
07/07/2023, 4:03 PMancient-minister-33499
07/07/2023, 4:07 PMapiVersion: <http://rke-machine.cattle.io/v1|rke-machine.cattle.io/v1>
kind: HarvesterMachineTemplate
metadata:
...
spec:
clusterName: mycluster1
template:
spec:
cloudConfig: null
clusterId: null
clusterType: null
common:
cloudCredentialSecretName: cattle-global-data:cc-kqr4b
...
vmNamespace: mynamespace
But this is one per pool. So there can be more than one entry.
and the harvester cluster id in its cloudCredentialSecretName .
In the secret this is in the harvestercredentialConfig-clusterId
apiVersion: v1
kind: Secret
metadata:
...
name: cc-kqr4b
namespace: cattle-global-data
data:
harvestercredentialConfig-clusterId: Yy1nbjZyZg==
....
Are these the best places to use?ancient-minister-33499
07/18/2023, 12:35 PMHarversterConfig
which is referenced in Cluster from provisioning.cattle.io/v1
e.g.
apiVersion: <http://rke-machine-config.cattle.io/v1|rke-machine-config.cattle.io/v1>
kind: HarvesterConfig
metadata:
name: nc-myCluster1-pool1-q2wzk
namespace: fleet-default
ownerReferences:
- apiVersion: <http://provisioning.cattle.io/v1|provisioning.cattle.io/v1>
blockOwnerDeletion: true
controller: true
kind: Cluster
name: myCluster1
...
...
vmNamespace: myNamespace