cluster-api-provider-tinkerbell
cluster-api-provider-tinkerbell copied to clipboard
Document why certain hardware metadata configuration is required
Followup to https://github.com/tinkerbell/cluster-api-provider-tink/pull/51#discussion_r612724952
Clarify to users why certain hardware metadata is required
- part is to satisfy cloud-init requirements for an ec2 style metadata source
- part is to allow CAPI to know which device to target when creating the template/workflow
Hey @detiber, just wanted to check and see if this is still an outstanding issue, yes?