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’ve encountered an interesting situation where I "hacked" (is it?) the operator to use the standby feature for replicating a standalone PostgreSQL database located on a remote server into my Kubernetes cluster. The source database's tables were in the postgres database.
The replication worked so well that the operator didn’t perform some expected tasks, specifically:
It didn’t create the database I specified in the preparedDatabase .
It didn’t create any users, even though defaultUsers: true was set.
Now that my data was "backed up" within my cluster. Does anybody know if there a way to make the operator to actually create these default users and database?
I would appreciate any guidance or clarification on how the operator handles such scenarios. Let me know if you need more details about my setup.
The text was updated successfully, but these errors were encountered:
Hello,
I’ve encountered an interesting situation where I "hacked" (is it?) the operator to use the standby feature for replicating a standalone PostgreSQL database located on a remote server into my Kubernetes cluster. The source database's tables were in the
postgres
database.The replication worked so well that the operator didn’t perform some expected tasks, specifically:
preparedDatabase
.defaultUsers: true
was set.Now that my data was "backed up" within my cluster. Does anybody know if there a way to make the operator to actually create these default users and database?
I would appreciate any guidance or clarification on how the operator handles such scenarios. Let me know if you need more details about my setup.
The text was updated successfully, but these errors were encountered: