From 2b4f2d2419893b1eac7e84462dfbbf03b1bdfeac Mon Sep 17 00:00:00 2001
From: Nick Vigilante <nick.vigilante@coder.com>
Date: Wed, 12 Aug 2026 21:37:25 +0000
Subject: [PATCH] docs: fix Helm TLS/ingress value keys in admin/setup

The setup guide used chart keys Helm silently ignores: coder.tls.secretName (singular) should be coder.tls.secretNames (a list), and coder.ingress.secretName/wildcardSecretName belong under coder.ingress.tls.{secretName,wildcardSecretName}. Also set coder.ingress.tls.enable so the ingress TLS example actually terminates TLS. Keys verified against helm/coder/values.yaml. Fixes DOCS-643.

> This PR was created with AI assistance (Coder Agents).
---
 docs/admin/setup/index.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/admin/setup/index.md b/docs/admin/setup/index.md
index a2c4fe776d3..8fd76ec4b34 100644
--- a/docs/admin/setup/index.md
+++ b/docs/admin/setup/index.md
@@ -99,12 +99,14 @@ working directory prior to step 1.
    ```yaml
    coder:
      tls:
-         secretName:
+       secretNames:
          - coder-tls
 
      # Alternatively, if you use an Ingress controller to terminate TLS,
      # set the following values:
      ingress:
+       enable: true
+       tls:
          enable: true
          secretName: coder-tls
          wildcardSecretName: coder-tls