You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1a. There is also the ssl: key in cr.yaml, where secret-names can be defined. Is it recommended to create the secrets with the names above or use other names and define them in ssl: ?
1b. The configuration-key ssl: is not explained in the docs above.
2c. When creating my-cluster-name-ssl , this seems also be used for internal connection. So what's the use-case to define different certificates and secrets? Even with splitHorizon , it is not neccessary to create and use different certificates.
The text was updated successfully, but these errors were encountered:
In https://github.com/percona/k8spsmdb-docs/blob/main/docs/TLS.md the manually created TLS-secrets are named
my-cluster-name-ssl-internal
andmy-cluster-name-ssl
.For me it is quite confusing:
1a. There is also the
ssl:
key incr.yaml
, where secret-names can be defined. Is it recommended to create the secrets with the names above or use other names and define them inssl:
?1b. The configuration-key
ssl:
is not explained in the docs above.2c. When creating
my-cluster-name-ssl
, this seems also be used for internal connection. So what's the use-case to define different certificates and secrets? Even with splitHorizon , it is not neccessary to create and use different certificates.The text was updated successfully, but these errors were encountered: