Skip to content

Update docs for global.tls.caKey #1900

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

Merged
david-yu merged 1 commit into from
Feb 22, 2023
Merged

Update docs for global.tls.caKey #1900

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 3 additions & 2 deletions charts/consul/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -364,8 +364,9 @@ global:
#
# Note that we need the CA key so that we can generate server and client certificates.
# It is particularly important for the client certificates since they need to have host IPs
# as Subject Alternative Names. In the future, we may support bringing your own server
# certificates.
# as Subject Alternative Names. If you are setting server certs yourself via `server.serverCert`
# and you are not enabling clients (or clients are enabled with autoEncrypt) then you do not
# need to provide the CA key.
caKey:
# The name of the Kubernetes or Vault secret that holds the CA key.
# @type: string
Expand Down