-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide option for change of owner of tables in Database which already exists #57
Comments
I have created a pull request for this topic :- #58. |
I think we already covered this in discussion on #58 - you can specify a masterRole that already owns the database and schemas and postgres-operator will not create a new owner role: postgres-operator/pkg/controller/postgres/postgres_controller.go Lines 146 to 149 in 243a5ec
It will then try to create this role and will just use the role provided in postgres-operator/pkg/postgres/role.go Lines 23 to 28 in 243a5ec
|
I know this issue is more than half and a year old but it seems I have the same problem, even using |
Currently when we apply Postgres CR it creates a DB if it doesn't exists and if it exists it changes its owner to the role created by the Postgres CRs. But the owner of the tables inside it remain unaltered due to which if we try to access it using credentials created by Postgres CRs then we get this error
It would be great if we get an option to migrate the owners of all the tables in the database to the role created by Postgres CRs
The text was updated successfully, but these errors were encountered: