-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Description
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
Metadata
Metadata
Assignees
Labels
No labels