TLS documentation mentions incorrect secrets specification in cr.yaml

Description

PSMDB operator documentation states in https://www.percona.com/doc/kubernetes-operator-for-psmongodb/TLS.html#generate-certificates-manually

You should generate certificates twice: one set is for external communications, and another set is for internal ones. A secret created for the external use must be added to cr.yaml/spec/secretsName. A certificate generated for internal communications must be added to the cr.yaml/spec/sslInternalSecretName.

In reality, the correct specification is different:

cr.yaml

Environment

None

Smart Checklist

Activity

Show:
Done

Details

Assignee

Reporter

Time tracking

1h 20m logged

Components

Fix versions

Priority

Smart Checklist

Created June 11, 2021 at 10:31 AM
Updated March 5, 2024 at 4:52 PM
Resolved June 18, 2021 at 12:31 PM