Open almahmoud opened 1 month ago
I wonder how this would affect an instance being upgraded from a galaxy helm chart version that uses the current solution with the Postgres operator to a newer helm chart version that uses this. It might be a lot of work for the people maintaining that instance. We would need a detailed and well tested process for that.
Sure, if we decide to do this, I agree we should provide some guidance on dumping and loading the database from the old to the new one. However, I also think even if it's a complicated process, that shouldn't stop us from improving the chart. Old users who don't want the change could either stay on a fixed version, or keep their old postgres and redeploy a new chart with postgres deployment disabled, connecting a new Galaxy chart to an existing postgres instance. Thus, I think it would be great to provide a way to move between them, but even if we can't provide a straightforward universal solution, I don't think that should keep us from choosing the better option going forward.
When looking at things for AnVIL, noticed that AKS uses CNPG for their managed Posgres CRDs, so given how well maintained and widely used it seems to be now, might be time to consider using that instead of the current one, although current one still seems maintained so maybe not urgent, but they also have charts to deploy CNPG operator