Add a note on how to provide installation hooks

Signed-off-by: David Cassany <[email protected]>
rancher · Oct 9, 2024 · f81b1ec · f81b1ec
1 parent a09f3b5
commit f81b1ec
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/docs/cloud-config-reference.md b/docs/cloud-config-reference.md
@@ -93,6 +93,9 @@ the preferred option is to build a [derivative image](custom-images.md) and not
   These stages are executed at end before exiting the command and running a cleanup process. At this stage the image is already deployed
   and locked in a read-only subvolume or filesystem. Partitions are still mounted at this stage.
 
+:::note
+Note installation hooks are not applied as part of the [MachineRegistartion.config.cloud-config](machineregistration-reference.md#config-cloud-config). In order to provide installation hooks they can be included as part of the [SeedImage.cloud-config](seedimage-reference.md#seedimagespec-reference), as they need to be present in the installation media.
+:::
 
 ## Configuration syntax
 

diff --git a/docs/machineregistration-reference.md b/docs/machineregistration-reference.md
@@ -49,6 +49,9 @@ spec:
 Contains the cloud-configuration to be injected in the node.  
 Both yip and cloud-init syntax are supported. See the [Cloud Config Reference](cloud-config-reference.md) for full information.
 
+The cloud-configuration provided in this field is not evaluated during the installation, it is
+just added to the node so it gets evaluated on reboot.
+
 #### config.network
 
 Contains the Declarative Networking configuration, supporting integration with [CAPI IPAM Providers](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20220125-ipam-integration.md#ipam-provider).