postgres-operator
postgres-operator copied to clipboard
movetokube
PostgreSQL operator for Kubernetes
This issue is second part of #31. Since the core business logic of this operator lies in SQL queries and combination of them, unit tests are not enough to test...
Currently there are no tests of any kind for the operator code, this issue addresses that. Test coverage should be at least 80% Just unit tests are fine as integration...
Closes #101. The whole usercontroller is not unit tested, so I did not add any tests.
Fixes #97 by moving to a namespaced role for the necessary things. This also encompasses #98's change.
It would be nice to be able to generate [connection strings](https://www.connectionstrings.com/postgresql/) as part of the secret to interoperate with .NET applications more easily
This is a massive change which I'm still working on. Not everything is ported to the new structure and I need to work on utils.Patch especially.
In general it sure seems like the RBAC here is very wide open. However, it still gave me an error on creation of the servicemonitor that the operator tries to...
lets the operator create a servicemonitor in its namespace
I suppose that originally provided `POSTGRES_URI_ARGS` should also be included into the generated secrets https://github.com/movetokube/postgres-operator/blob/e71c0d1c75a4888a8170d7859d07686c55663840/pkg/controller/postgresuser/postgresuser_controller.go#L266-L267 ex: `sslmod=disable` I can make PR but it will not be very soon.
We would like to be able to set limits on the max. connections in databases or roles. In psql that would be for example: ``` alter database mydb connection limit...
