TELCODOCS-450: Added warning admonishment for TLS enablement with regard to the HTTPD server

Author: kdrake20

modules/ipi-install-creating-an-rhcos-images-cache.adoc

@@ -15,6 +15,11 @@ The installation program no longer needs the `clusterOSImage` {op-system} image
 
 If you are running the installation program on a network with limited bandwidth and the {op-system} images download takes more than 15 to 20 minutes, the installation program will timeout. Caching images on a web server will help in such scenarios.
 
+[WARNING]
+====
+If you enable TLS for the HTTPD server, you must confirm the root certificate is signed by an authority trusted by the client and verify the trusted certificate chain between your {product-title} hub and spoke clusters and the HTTPD server. Using a server configured with an untrusted certificate prevents the images from being downloaded to the image creation service. Using untrusted HTTPS servers is not supported.
+====
+
 Install a container that contains the images.
 
 .Procedure
@@ -133,4 +138,4 @@ platform:
 ----
 <1> Replace `<bootstrap_os_image>` with the value of `$BOOTSTRAP_OS_IMAGE`.
 +
-See the "Configuring the install-config.yaml file" section for additional details.
+See the "Configuring the install-config.yaml file" section for additional details.

modules/ztp-configuring-the-cluster-for-a-disconnected-environment.adoc

@@ -14,6 +14,11 @@ After you have completed the preceding procedure, follow these steps to configur
 
 * Host the `rootfs` and `iso` images on an HTTPD server.
 
+[WARNING]
+====
+If you enable TLS for the HTTPD server, you must confirm the root certificate is signed by an authority trusted by the client and verify the trusted certificate chain between your {product-title} hub and spoke clusters and the HTTPD server. Using a server configured with an untrusted certificate prevents the images from being downloaded to the image creation service. Using untrusted HTTPS servers is not supported.
+====
+
 .Procedure
 
 . Create a `ConfigMap` containing the mirror registry config:
@@ -86,4 +91,4 @@ You can do this by configuring chrony to act as server, editing the `/etc/chrony
 local stratum 10
 bindcmdaddress ::
 allow 2620:52:0:1310::/64
-----
+----