Add ability to specify a user data file

[AlexSchultz-clumio]

Issue #, if available:

Description of changes:

Sometimes we need to execute some actions on the instance along with the eks build script but currently there is not a way to inject these additional steps as part of the existing build process. This change adds the ability to specify user_data_file which can be passed to the build instance on startup.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing Done

Built a new image with make k8s=1.29 user_data_file=test.yaml

The test.yaml contained several bootcmd and runcmd options to tweak the base image being used:

#cloud-config
bootcmd:
  # remove possible fips incompatible ciphers
  - sed -i -e 's/curve25519-sha256@libssh.org[,]*//' -e 's/curve25519-sha256[,]*//' /etc/ssh/sshd_config
  # remove ip_forward disabling from CIS image
  - sed -i -e '/net.ipv4.ip_forward/d' /etc/sysctl.conf
runcmd:
  # open access to kubelet
  - iptables -A INPUT -p tcp -m tcp --dport 10250 -m state --state NEW -j ACCEPT
  # open access for NodePorts
  - iptables -A INPUT -p tcp -m multiport --dports 30000:32767 -j ACCEPT
  # save updated iptables
  - bash -c "/sbin/iptables-save > /etc/sysconfig/iptables"

Deployed built AMI to cluster and verified pods were able to be schedule and use the node. Also verified the actions were run during the build process and the results showed up in the built AMI.

[cartermckinnon]

I think this is a great idea. Way better than patching in a custom provisioner or maintaining a full fork of the template.

@ndbaker1 @Issacwww please weigh in

[ndbaker1]

i agree! nice way to help decouple

[AlexSchultz-clumio]

@cartermckinnon since this is an acceptable improvement, can we merge this?

[cartermckinnon]

/ci build

[github-actions]

@cartermckinnon roger that! I've dispatched a workflow. 👍

[github-actions]

@cartermckinnon the workflow that you requested has completed. 🎉

AMI variant	Build	Test
1.23 / al2	failure ❌	skipped ⏭️
1.23 / al2023	failure ❌	skipped ⏭️
1.24 / al2	failure ❌	skipped ⏭️
1.24 / al2023	failure ❌	skipped ⏭️
1.25 / al2	failure ❌	skipped ⏭️
1.25 / al2023	failure ❌	skipped ⏭️
1.26 / al2	failure ❌	skipped ⏭️
1.26 / al2023	failure ❌	skipped ⏭️
1.27 / al2	failure ❌	skipped ⏭️
1.27 / al2023	failure ❌	skipped ⏭️
1.28 / al2	failure ❌	skipped ⏭️
1.28 / al2023	failure ❌	skipped ⏭️
1.29 / al2	failure ❌	skipped ⏭️
1.29 / al2023	failure ❌	skipped ⏭️

[cartermckinnon]

@AlexSchultz-clumio you need to add a default value for this variable in the respective variables-default.json file for each template:

1 error occurred:
	* required variable not set: user_data_file

Empty string should do it 👍

[AlexSchultz-clumio]

Got it. Will fix thanks

[cartermckinnon]

/ci

[github-actions]

@cartermckinnon roger that! I've dispatched a workflow. 👍

[github-actions]

@cartermckinnon the workflow that you requested has completed. 🎉

AMI variant	Build	Test
1.23 / al2	success ✅	success ✅
1.23 / al2023	success ✅	success ✅
1.24 / al2	success ✅	success ✅
1.24 / al2023	success ✅	success ✅
1.25 / al2	success ✅	success ✅
1.25 / al2023	success ✅	success ✅
1.26 / al2	success ✅	success ✅
1.26 / al2023	success ✅	success ✅
1.27 / al2	success ✅	success ✅
1.27 / al2023	success ✅	success ✅
1.28 / al2	success ✅	success ✅
1.28 / al2023	success ✅	success ✅
1.29 / al2	success ✅	success ✅
1.29 / al2023	success ✅	success ✅