From 6da77ad102b3401fc239f276f7f7b7f5de68ad6b Mon Sep 17 00:00:00 2001 From: Micah Nagel Date: Mon, 18 Nov 2024 10:40:38 -0700 Subject: [PATCH] docs: chatgpt rewording --- docs/reference/configuration/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/configuration/ingress.md b/docs/reference/configuration/ingress.md index 17a587635..8fab9abfe 100644 --- a/docs/reference/configuration/ingress.md +++ b/docs/reference/configuration/ingress.md @@ -76,7 +76,7 @@ packages: You can then either use environment variables (`UDS_ADMIN_TLS_CERT`, `UDS_ADMIN_TLS_KEY`, `UDS_TENANT_TLS_CERT`, and `UDS_TENANT_TLS_KEY`) or a config file to configure the certs for each gateway. These values should be base64 encoded strings of the TLS certificate and key for the admin and tenant gateways respectively. :::note -The values you provide for `TLS_CERT` configuration values should include both your specific domain cert (i.e. `*.uds.dev`) as well as the full chain of certs back to a trusted root CA (concatenated together). If you do not provide the full chain you may experience unexpected behavior with certain applications as not all container images will trust intermediate certificates by default. +The `TLS_CERT` configuration values must include your specific domain certificate (e.g., `*.uds.dev`) **and** the full certificate chain leading up to a trusted root Certificate Authority (CA), concatenated together. Failing to include the full chain can result in unexpected behavior with certain applications, as some container images may not inherently trust intermediate certificates. ::: Domain should be set via your [uds-config](https://uds.defenseunicorns.com/reference/cli/quickstart-and-usage/#variables-and-configuration) file using the shared key to override the Zarf Domain Variable (see example `uds-config.yaml` below).