mirror of
https://github.com/bitnami/charts.git
synced 2026-03-08 08:47:24 +08:00
[bitnami/cassandra] Amend cassandra TLS documentation (#8694)
* Amend cassandra TLS documentation Signed-off-by: Fran Mulero <fmulero@vmware.com>
This commit is contained in:
@@ -23,4 +23,4 @@ name: cassandra
|
||||
sources:
|
||||
- https://github.com/bitnami/bitnami-docker-cassandra
|
||||
- http://cassandra.apache.org
|
||||
version: 9.1.0
|
||||
version: 9.1.1
|
||||
|
||||
@@ -304,10 +304,10 @@ Bitnami will release a new chart updating its containers if a new version of the
|
||||
|
||||
This chart supports TLS between client and server and between nodes, as explained below:
|
||||
|
||||
* For internode cluster encryption, set the `cluster.internodeEncryption` chart parameter to a value different from `none`. Available values are `all`, `dc` or `rack`.
|
||||
* For client-server encryption, set the `cluster.clientEncryption` chart parameter to `true`.
|
||||
* For internode cluster encryption, set the `tls.internodeEncryption` chart parameter to a value different from `none`. Available values are `all`, `dc` or `rack`.
|
||||
* For client-server encryption, set the `tls.clientEncryption` chart parameter to `true`.
|
||||
|
||||
In both cases, it is also necessary to create a secret containing the keystore and truststore certificates and their corresponding protection passwords. This secret is to be passed to the chart via the `tlsEncryptionSecretName` parameter at deployment-time.
|
||||
In both cases, it is also necessary to create a secret containing the keystore and truststore certificates and their corresponding protection passwords. This secret is to be passed to the chart via the `tls.existingSecret` parameter at deployment-time.
|
||||
|
||||
Refer to the chart documentation for more [information on creating the secret and a TLS deployment example](https://docs.bitnami.com/kubernetes/infrastructure/cassandra/administration/enable-tls/).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user