luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Clarifies external CA config 

It is not clear that this page is to configure an external CA for Connect CA. Added line to clarify that this page is for configuring external CA's for the Connect CA. For the built-in CA, no config is needed.
This commit is contained in:
vanphan24 2022-01-11 13:22:50 -08:00 committed by GitHub
parent 733526a012
commit 2c0a87a057
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/content/docs/k8s/connect/connect-ca-provider.mdx
View File

@ -14,7 +14,8 @@ Consul has support for different certificate authority (CA) providers to be used
Please see [Connect Certificate Management](/docs/connect/ca) for the information on the providers Please see [Connect Certificate Management](/docs/connect/ca) for the information on the providers
we currently support. we currently support.
To configure a provider via the Consul Helm chart, you need to follow three steps: If Connect is enabled, the built-in Consul CA is automatically enabled for the Connect CA.
To configure an external CA provider via the Consul Helm chart, you need to follow three steps:
1. Create a configuration file containing your provider information. 1. Create a configuration file containing your provider information.
1. Create a Kubernetes secret containing the configuration file. 1. Create a Kubernetes secret containing the configuration file.