You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue with the CloudNativePG operator where the enableSuperuserAccess feature does not create the specified superuser secret (superuserSecret) containing the credentials for the postgres user. This behavior is unexpected based on the documentation, which states that enabling enableSuperuserAccess should result in the creation of a secret when it does not already exist.
Here is my configuration:
Cluster Specification:
apiVersion: postgresql.cnpg.io/v1kind: Clustermetadata:
name: postgres-clusternamespace: postgresspec:
enableSuperuserAccess: truesuperuserSecret:
name: postgres-superuserinstances: 3bootstrap:
initdb:
database: temporalowner: temporal_adminpostInitSQL:
- ALTER USER temporal_admin WITH SUPERUSER;
Chart Values:
cluster:
fullnameOverride: postgres-clustercluster:
instances: 3storage:
size: 8Giinitdb:
database: temporalowner: temporal_adminpostInitSQL:
- ALTER USER temporal_admin WITH SUPERUSER;
Despite enabling enableSuperuserAccess and specifying postgres-superuser as the superuserSecret, no secret is created, and I am not aware of the password for the postgres superuser account. This creates a roadblock when I need to perform administrative tasks or create new users and databases.
Expected Behavior:
When enableSuperuserAccess: true is set, the operator should:
Automatically create the specified superuserSecret if it does not already exist.
Store the postgres user's password in this secret for later retrieval.
Additional Requirement:
I also want to create a new user dapr_admin and a database dapr where dapr_admin is the owner. Since I do not have the password for the postgres user, I am unable to execute these actions.
Steps to Reproduce:
Deploy the cluster with the following configuration:
enableSuperuserAccess: true
superuserSecret: postgres-superuser
Verify if the postgres-superuser secret is created in the namespace.
Try to retrieve the postgres user's password from the secret.
Issue Description:
I am encountering an issue with the CloudNativePG operator where the enableSuperuserAccess feature does not create the specified superuser secret (superuserSecret) containing the credentials for the postgres user. This behavior is unexpected based on the documentation, which states that enabling enableSuperuserAccess should result in the creation of a secret when it does not already exist.
Here is my configuration:
Cluster Specification:
Chart Values:
Despite enabling
enableSuperuserAccess
and specifyingpostgres-superuser
as thesuperuserSecret
, no secret is created, and I am not aware of the password for the postgres superuser account. This creates a roadblock when I need to perform administrative tasks or create new users and databases.Expected Behavior:
When enableSuperuserAccess: true is set, the operator should:
Additional Requirement:
I also want to create a new user dapr_admin and a database dapr where dapr_admin is the owner. Since I do not have the password for the postgres user, I am unable to execute these actions.
Steps to Reproduce:
Environment Details:
Helm Chart Version: 0.1.0
Kubernetes Version: [v1.30.3+k3s1]
Cluster Namespace: postgres
Workaround Needed:
Please provide a way to:
Thank you for your support!
The text was updated successfully, but these errors were encountered: