postgresqlPassword is expected even if using postgresqlExistingSecret about charts HOT 6 CLOSED

No I was trying to use the internal DB and inject passwords with existing secrets. It wasn't clear from the comments/docs that this wasn't supported.

Awesome, I started going through the postgresql helm chart options to solve it but you got there first.

I wasn't able to get it to work. If I deploy awx and postgresql as separate helm charts everything works fine. I've also had success with the new operator so I'm not going to worry too much about it. Below is the last values.yaml file I tried. Everything deployed but the web container never connected to the DB. I had to create two separate pgsql secrets due to different information being required. ``` defaultAdminExistingSecret: awx-admin-creds postgresql: enabled: true postgresqlPassword: "" volumePermissions: enabled: true existingSecret: pgsql-creds secretKeyExistingSecret: awx-secret-key postgresqlExistingSecret: awx-pgsql-creds ``` I had to create two separate pgsql secrets due to different information being required. ``` kubectl create secret generic awx-pgsql-creds \ --from-literal=DATABASE_USER=awx \ --from-literal=DATABASE_NAME=awx \ --from-literal=DATABASE_HOST=postgresql \ --from-literal=DATABASE_PORT=5432 \ --from-literal=DATABASE_PASSWORD=test \ --from-literal=DATABASE_ADMIN_PASSWORD=test kubectl create secret generic pgsql-creds \ --from-literal=postgresql-password=test \ --from-literal=postgresql-postgres-password=test ```