Goal

The cloud-init NoCloud datasource allows hypervisors to provide configuration data for the guest as so called vendor-data [1]. This would for example allow to inject activation data (cluster license), global SSH public keys known/stored by the hypervisor, etc. into a guest.

User Stories

• As a Cluster Admin, I want to provide activation data for RHEL guests, so that RHEL guests running on the cluster get activated automatically and the VM owners does not have to specify the activation keys in the cloud-init of the VM spec.
• As a Cluster Admin, I want to provide common SSH public keys in one place, so that all guests running on the cluster can be accessed with them, in addition to the public keys of the VM owners.
• As a Cluster Admin I want to inject activation data into RHEL VMs on my cluster, so that VMs can use the OpenShift license of the cluster.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• See the upstream issue for a further explanation
• This is motivated by the UI having to use older network formats because the access credentials API mandates the use of ConfigDrives as cloud-init datasource.
• See https://issues.redhat.com/browse/CNV-31980 as preliminary step