Skip to content

Commit 8b13a47

Browse files
Update docs/reference/template-functions-static-context.md
Co-authored-by: Ethan Mosbaugh <[email protected]>
1 parent 1d3f2ad commit 8b13a47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/reference/template-functions-static-context.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ PrivateCACert returns the name of the ConfigMap even if the ConfigMap has no ent
2828

2929
KOTS mounts the ConfigMap returned by the PrivateCACert template function as a volume in the kotsadm container at `/certs`. Each key in the ConfigMap is created as a file, with its value as the file's contents. KOTS then sets the `SSL_CERT_DIR` environment variable in the kotsadm container to `/certs`. `SSL_CERT_DIR` is a common environment variable that is supported by most tools and languages to override the trust store.
3030

31-
The primary use case for the PrivateCACert template function is to make sure that KOTS trusts the private CA certificates issued by TLS proxies in the end user's environment and can make outbound internet connects without TLS errors.
31+
The primary use case for the PrivateCACert template function is to make sure that KOTS trusts the private CA certificates issued by TLS man-in-the-middle proxies in the end user's environment and can make outbound internet connects without TLS errors.
3232

3333
<details>
3434
<summary>Can the ConfigMap returned by PrivateCACert also be mounted in application containers?</summary>

0 commit comments

Comments
 (0)