Skip to content

Commit 4ceb4d5

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

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
@@ -24,7 +24,7 @@ For Replicated Embedded Cluster installations on VMs or bare metal servers, you
2424
* Set the `NODE_EXTRA_CA_CERTS` environment variable to append the CAs from the ConfigMap to any existing CAs in the container
2525
* Mount the CAs at `/certs` and set the `SSL_CERT_DIR` environment variable to `/certs`
2626

27-
For existing cluster installations with KOTS, KOTS automatically mounts the ConfigMap as a volume in the kotsadm container at `/certs`. Each key in the ConfigMap is created as a file, with its value as 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 append certificates to the trust store.
27+
For existing cluster installations with KOTS, KOTS automatically mounts the ConfigMap as a volume in the kotsadm container at `/certs`. Each key in the ConfigMap is created as a file, with its value as 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.
2828

2929
<details>
3030
<summary>Where does the ConfigMap returned by the PrivateCACert template function come from?</summary>

0 commit comments

Comments
 (0)