EKSA Baremetal tinkerbell support custom actions in TinkerbellTemplateConfig

[saiteja313]

What would you like to be added:

• Support custom action into the TinkerbellTemplateConfig to install custom packages into the node following the official documentation: https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/bare-spec/#custom-tinkerbell-action-examples

• A fix was merged for this support in upstream tinkerbell - https://github.com/tinkerbell/hook/pull/200.

Workaround:

1. EKSA Admins can use the upstream built HookOS files with EKS-A here: https://github.com/tinkerbell/hook/releases/download/latest/hook_x86_64.tar.gz.
2. EKSA Cluster admins can download the archive and extract the contents to a location that is being served via HTTP.
3. The directory format to follow is found here: https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/bare-spec/#example-tinkerbelldatacenterconfigspec
4. EKSA Admin should specify the location where they have hosted the files in the cluster config:

   TinkerbellDatacenterConfig.spec.hookImagesURLPath: "http://my-web-server/hook"

   Why is this needed:

   • Support custom action into the TinkerbellTemplateConfig to install custom packages into the node

[terry-hasegawa]

I also vote to update the hook. The EKS-A HookOS is old. We are now using newer servers. It requires an upstream built HookOS.