docs: redpanda-superuser secret contents

[fstr]

If I don't provide auth.sasl.secretRef but a list of users via auth.sasl.users, the {{ clusterName }}-superuser secret will be created by the operator. The operator uses a property called users.txt. Code is here. Its contents will look like this:

% k get secret redpanda-superuser -o yaml
apiVersion: v1
data:
  users.txt: <some base64 encoded u:p:mechanism string>

The user is also added to the list of superusers:

% k exec -ti redpanda-1 -c redpanda -- rpk cluster config get superusers
- bootstrap-user
- florian <---------------------- HERE

The example in the docs mentions that the superusers should be added to a property called superusers.txt: https://docs.redpanda.com/current/manage/kubernetes/security/authentication/k-authentication/#use-a-secret-resource

Should it be users.txt or superusers.txt or doesn't it matter?

Environment:

• Operator: v25.1.3
• Redpanda: v25.2.5
• Kubernetes: 1.33

[gabschne]

Should it be users.txt or superusers.txt or doesn't it matter?

Unofficial (and presumably unqualified) answer: The key(s) in the secret seems to be irrelevant. I use credentials.

I guess the secret is simply mounted and the files (which exist per key in the secret) are filtered for the relevant entries.

[qlikcoe]

I agree, that filename discrepancy is confusing.