Skip to content

docs: document applyInternalDNSNames for custom-issuer TLS (DOC-182) #1889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JakeSCahill wants to merge 2 commits into
base: main
Choose a base branch
from
+17 −0
Open

docs: document applyInternalDNSNames for custom-issuer TLS (DOC-182) #1889

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
492ec1a
docs: document applyInternalDNSNames for custom-issuer TLS (DOC-182)
JakeSCahill Aug 6, 2026
17eae09
fix(k8s-tls): set caEnabled to true in the private-CA example
JakeSCahill Aug 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions modules/manage/pages/kubernetes/security/tls/k-cert-manager.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -303,6 +303,23 @@ helm upgrade --install redpanda redpanda/redpanda --namespace <namespace> --crea
====
include::manage:partial$kubernetes/tls-update-note.adoc[]
====
+
When you provide your own Issuer, the Helm chart does not add the brokers' internal Kubernetes Service addresses to the Certificate, because public CAs such as Let's Encrypt cannot issue certificates for cluster-local names. If your Issuer is a private CA that can issue certificates for internal addresses, set `applyInternalDNSNames` to `true`. This setting adds the internal addresses to the Certificate so that clients inside the Kubernetes cluster can validate connections to the internal listeners with the same Certificate.
+
Because a private CA is not publicly trusted, also set `caEnabled` to `true`. The chart then uses the `ca.crt` file in the Certificate's Secret for the listener trust stores and for chart-managed clients such as `rpk`. When `caEnabled` is `false`, listeners fall back to the container's CA certificates, which do not trust your private CA.
+
[,yaml]
----
tls:
enabled: true
certs:
external:
issuerRef:
name: <issuer-name>
kind: <issuer>
applyInternalDNSNames: true
caEnabled: true
----

. Make sure the Certificates are in a `READY` state.
+
Expand Down
Loading