OEM: IONOS Cloud Images #29
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds IONOS Cloud custom provider
This aims to keep supporting basic Cloud-Init functionality with Flatcar by introducing the IONOS Cloud provider. As the IONOS Cloud was built on top of the idea of cloud-init all of our utilities and customers use it. Therefore we want to have basic feature support to not force everyone to switch to ignition
How to use
Use the IONOS Cloud Flatcar image to create a VM and inject Cloud-Init User Data:
https://docs.ionos.com/cloud/storage-and-backup/block-storage/images-snapshots/boot-cloud-init
Use the
#cloud-config
directive!Testing done
Used the Image built from flatcar/scripts#2389 and inject a basic cloud-config script:
And checked if the file exists after the first boot.
PR Requirements
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.