Merge pull request #92128 from amolnar-rh/TELCODOCS-2195

TELCODOCS-2195#Add note about correct sync-wave for optional override BMH in SiteConfig

Author: maxwelldb

modules/ztp-deploying-a-site.adoc

@@ -77,6 +77,11 @@ include::snippets/ztp_example-sno.yaml[]
 ====
 For more information about BMC addressing, see the "Additional resources" section. The `installConfigOverrides` and  `ignitionConfigOverride` fields are expanded in the example for ease of readability.   
 ====
++
+[NOTE]
+====
+To override the default `BareMetalHost` CR for a node, you can reference the override CR in the node-level `crTemplates` field in the `SiteConfig` CR. Ensure that you set the `argocd.argoproj.io/sync-wave: "3"` annotation in your override `BareMetalHost` CR.
+====
 
 .. You can inspect the default set of extra-manifest `MachineConfig` CRs in `out/argocd/extra-manifest`. It is automatically applied to the cluster when it is installed.
 

snippets/ztp_example-sno.yaml

@@ -76,6 +76,8 @@ spec:
           bootMode: "UEFISecureBoot"
           rootDeviceHints:
             deviceName: "/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0"
+          #crTemplates:
+          #  BareMetalHost: "bmhOverride.yaml"
           # disk partition at `/var/lib/containers` with ignitionConfigOverride. Some values must be updated. See DiskPartitionContainer.md for more details
           ignitionConfigOverride: |
             {