Custom extra cloud-init userdata

sleterrier commented 2 years ago

What would you like to be added: Option to provide extra cloud-init user-data to cluster nodes.

VSphereMachineConfig, CloudStackMachineConfig, TinkerbellMachineConfig all implement spec.users which eventually get merged in cloud-init user-data. Would it be possible to add a new field (e.g. spec.extraUserData) allowing for free form cloud-init customization?

Why is this needed: There are many use-cases, but here are a couple examples:

Custom container runtime configuration (e.g. set registry-mirror to pull images from local registry first by default)
Trust private Certification Authority
Custom agent installation (configuration management, auditing/security tools, etc...)

The official documentation recommends those changes to be made on the template itself. It works, but requires multiple images to be maintained (and distributed to their proper location) if customization defers between node types and/or clusters.

TerryHowe commented 2 years ago

The CA use case has definitely come up before. I think this is a good idea.

danbudris commented 2 years ago

Let's keep this open to gauge interest; please 👍 this issue to indicate interest in the feature

Paulius0112 commented 1 year ago

Hi. Is it currently possible to pass a self-signed registry certificate in bare metal bottlerocket? We need it for pulling images from private registry, since providing certificate under registryMirrorConfiguration.caCertContent doesn't solve this problem.

aws / eks-anywhere

Custom extra cloud-init userdata #4223