docs: clarification on Limitations for Vault Secrets backend (#11885)

* docs: clarification on Limitations for Vault Secrets backend

* address typo in CLI docs

* Update index.mdx

* Update index.mdx
This commit is contained in:
David Yu 2021-12-17 14:38:12 -08:00 committed by GitHub
parent bd011ab7b6
commit 2df20d13d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 4 deletions

View File

@ -38,9 +38,8 @@ injector:
- `global.tls.serverAdditionalIPSans` is not currently configurable and must be manually added to the server certificate in Vault. - `global.tls.serverAdditionalIPSans` is not currently configurable and must be manually added to the server certificate in Vault.
- Mesh gateway is not currently supported. - Mesh gateway is not currently supported.
- Multi-DC Federation is not currently supported. - Multi-DC Federation is not currently supported.
- Certificate rotation is not currently supported, ensure the TTL for your certificates is sufficiently long. Should your certificates - Certificate rotation for Server TLS certs is not currently supported through the Helm chart. Ensure the TTL for your Server TLS certificates are sufficiently long. Should your certificates expire it will be necessary to issue a `consul reload` on each server after issuing new Server TLS certs from Vault.
expire it will be necessary to issue a `consul reload` on each server. - CA rotation is not currently supported through the Helm chart and must be manually rotated.
- CA rotation is not currently supported.
## Next Steps ## Next Steps

View File

@ -170,7 +170,7 @@ $ consul-k8s status
metrics: metrics:
defaultEnableMerging: true defaultEnableMerging: true
defaultEnabled: true defaultEnabled: true
enableGatewayMetrics: trueU enableGatewayMetrics: true
controller: controller:
enabled: true enabled: true
global: global: