doc: update for ionoscloud provider

Signed-off-by: Jan Larwig <[email protected]>

Author: tuunit

docs/supported-platforms.md

@@ -20,7 +20,7 @@ Ignition is currently supported for the following platforms:
 * [Hetzner Cloud] (`hetzner`) - Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.
 * [Microsoft Hyper-V] (`hyperv`) - Ignition will read its configuration from the `ignition.config` key in pool 0 of the Hyper-V Data Exchange Service (KVP). Values are limited to approximately 1 KiB of text, so Ignition can also read and concatenate multiple keys named `ignition.config.0`, `ignition.config.1`, and so on.
 * [IBM Cloud] (`ibmcloud`) - Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.
-* [IONOS Cloud] (`ionoscloud`) - Ignition will read its configuration from the instance user-data. Per default the user-data are injected on a disk or partition with the label `OEM` which can be customized using the environment variable `IGNITION_CONFIG_DEVICE_LABEL`. 
+* [IONOS Cloud] (`ionoscloud`) - Ignition will read its configuration from an injected user-data file. Per default the user-data is injected in a disk or partition with the label `OEM` and location `/config/user-data`. If this is different for your image build process or configuration you can customize the location for fetching the data using the kernel flags `deviceLabelKernelFlag` and `userDataKernelFlag`.
 * [KubeVirt] (`kubevirt`) - Ignition will read its configuration from the instance userdata via config drive. Cloud SSH keys are handled separately.
 * Bare Metal (`metal`) - Use the `ignition.config.url` kernel parameter to provide a URL to the configuration. The URL can use the `http://`, `https://`, `tftp://`, `s3://`, `arn:`, or `gs://` schemes to specify a remote config.
 * [Nutanix] (`nutanix`) - Ignition will read its configuration from the instance userdata via config drive. Cloud SSH keys are handled separately.

internal/providers/ionoscloud/ionoscloud.go

@@ -14,12 +14,15 @@
 //
 // NOTE: This provider is still EXPERIMENTAL.
 //
-// The IONOS Cloud provider fetches the ignition config from the user-data
-// available in an injected file at /var/lib/cloud/seed/nocloud/user-data.
+// The IONOS Cloud provider fetches the ignition config from a user-data file.
 // This file is created by the IONOS Cloud VM handler before the first boot
-// through the cloud init user data handling.
+// and gets injected into a device at /config/user-data by default.
 //
-// User data with the directive #cloud-config will be ignored
+// The kernel parameters deviceLabelKernelFlag and userDataKernelFlag can be
+// used during the build process of images and for the VM initialization to
+// specify on which disk or partition the user-data is going to be injected.
+//
+// User data files with the directive #cloud-config and #!/bin/ will be ignored
 // See for more: https://docs.ionos.com/cloud/compute-services/compute-engine/how-tos/boot-cloud-init
 
 package ionoscloud
@@ -48,7 +51,7 @@ const (
 	deviceLabelKernelFlag = "ignition.config.device"
 	defaultDeviceLabel    = "OEM"
 	userDataKernelFlag    = "ignition.config.path"
-	defaultUserDataPath   = "config.ign"
+	defaultUserDataPath   = "config/user-data"
 )
 
 func init() {