Populate HardwareRef when creating workflows

The latest version of tink adds a HardwareRef field to workflows that
enables Hardware data to be exposed to the workflow's template during
rendering.

Signed-off-by: Chris Doherty <chris.doherty4@gmail.com>

Author: chrisdoherty4

config/default/kustomization.yaml

@@ -11,20 +11,19 @@ commonLabels:
   cluster.x-k8s.io/provider: infrastructure-tinkerbell
 
 resources:
-- namespace.yaml
+  - namespace.yaml
 
 bases:
-- ../crd
-- ../rbac
-- ../manager
-- ../webhook
-- ../certmanager
+  - ../crd
+  - ../rbac
+  - ../manager
+  - ../webhook
+  - ../certmanager
 
 patchesStrategicMerge:
-- manager_image_patch.yaml
-- manager_pull_policy.yaml
-- manager_webhook_patch.yaml
-- webhookcainjection_patch.yaml
+  - manager_image_patch.yaml
+  - manager_webhook_patch.yaml
+  - webhookcainjection_patch.yaml
 
 vars:
   - name: CERTIFICATE_NAMESPACE # namespace of the certificate CR

config/default/manager_pull_policy.yaml

@@ -675,6 +675,7 @@ func (mrc *machineReconcileContext) createWorkflow(hardware *tinkv1.Hardware) er
 		},
 		Spec: tinkv1.WorkflowSpec{
 			TemplateRef: mrc.tinkerbellMachine.Name,
+			HardwareRef: hardware.Name,
 			HardwareMap: map[string]string{"device_1": hardware.Spec.Metadata.Instance.ID},
 		},
 	}