default users secret name is not ok

Description

I have disabled the secrets section in cr.yaml completely to see what operator will generate by default, this is what I got:

As you can see the users secret doesn't include the cluster name, but operator name which is not optimal.

It is set here: https://github.com/percona/percona-server-mongodb-operator/blob/main/pkg/apis/psmdb/v1/psmdb_defaults.go#L27

Also internal secrets have inconsistent naming, check this:

one is called "internal-my-cluster-name-users" and the other one is "my-cluster-name-ssl-internal" so one uses internal as prefix and the other one as suffix.

Environment

None

Smart Checklist

Activity

Slava Sarzhan September 18, 2023 at 1:45 PM

I am okay with fixing user's secret name but I am not sure about 
'-internal' prefix/suffix because we have the same approach for all our operators. what do you think about it?

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created December 23, 2021 at 4:38 PM
Updated October 3, 2024 at 3:08 PM