-
Notifications
You must be signed in to change notification settings - Fork 574
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
Allow postgres extensions #4
Comments
Or change the docker image that operator uses to deploy postgres, such as using this instead of native docker image |
You'll be able to find out more information about deploying a customized strategy here: https://github.com/CrunchyData/postgres-operator/blob/master/docs/design.asciidoc Inside of the strategy templates, you can either modify these directly or create a new folder called "2" where these files are copied over and modified to fit your needs. https://github.com/CrunchyData/postgres-operator/tree/master/conf/postgres-operator/cluster/1 The pgo configuration file starts out here and is (during the installation step) moved to your $HOME directory if you followed the default location provided in the instructions. For more information about modifying the configuration file, please take a look at the Configuration file here: https://github.com/CrunchyData/postgres-operator/blob/master/docs/config.asciidoc but you should see the section STRATEGY: 1 where you would simply change that variable to "2". I hope that helps! |
the base image is something you could change by editing the various templates used by the operator, we have for instance a postgres-gis container image that include postgis, if you were to replace the current image name in the configuration it would deploy that container image instead of the default postgres image. |
User should be able to install and enable extensions such as
postgis
within postgres instances that operator createsThe text was updated successfully, but these errors were encountered: