Skip to content
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.

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

handling with manually created certficates a bit confusing #60

Open
rdxmb opened this issue May 16, 2023 · 0 comments
Open

handling with manually created certficates a bit confusing #60

rdxmb opened this issue May 16, 2023 · 0 comments

Comments

@rdxmb
Copy link

rdxmb commented May 16, 2023

In https://github.com/percona/k8spsmdb-docs/blob/main/docs/TLS.md the manually created TLS-secrets are named my-cluster-name-ssl-internal and my-cluster-name-ssl.

For me it is quite confusing:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant