How can I use a custom image for the postgres container only?

[jarrettprosser]

I'm using the 4.5.1 operator and need to install some extensions in the Postgres image. I can see this is being asked about in #2016, but in the meantime I was going to try and use a custom image that I maintain with the required extensions installed. How can I configure the operator to use a private registry with a custom Postgres image, while using the public images for all the other containers?

Thanks!

[jkatz]

Which extensions are you looking to install?

[jarrettprosser]

In one instance pg_partman, and in another timescaledb.

[fgielow]

I share interest in compiling a custom image with timescaleDB.

[moimart1]

I follow instruction here: #2189 (comment)

With this Dockerfile

ARG FROM_IMAGE=registry.developers.crunchydata.com/crunchydata/crunchy-postgres-ha:centos7-12.5-4.5.1
FROM ${FROM_IMAGE}

USER root
RUN curl -sSL -o /etc/yum.repos.d/timescale_timescaledb.repo "https://packagecloud.io/install/repositories/timescale/timescaledb/config_file.repo?os=el&dist=7" && \
    yum --disablerepo=crunchypg12 update -y && \
    yum --disablerepo=crunchypg12 install -y timescaledb-2-postgresql-12 && \
    yum clean all

RUN sed -i '/shared_preload_libraries:/ s/$/,timescaledb/' /opt/cpm/conf/postgres-ha-initdb.yaml && \
    sed -i '/\\c "\${PGHA_DATABASE}"$/a CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;' /opt/cpm/bin/sql/setup.sql

USER postgres

Then I push my custom image and run this command:

pgo create cluster hippo --ccp-image-prefix <my-registry> --ccp-image crunchy-postgres-ha --ccp-image-tag centos7-12.5-4.5.1

I connect to hippo db and I be able to create hyper_table (https://docs.timescale.com/latest/getting-started/creating-hypertables)

I don't know if it's a good solution, but it seems work :)

[jarrettprosser]

Thanks @moimart1, that's close to what I need. The last missing piece is that I have a private registry. Can I pass imagePullSecrets to the operator somehow to allow access to a private registry? There's a guide to adding secrets here, but it's for the operator image, not the database image.

[jkatz]

#2193 (comment)

Both of these extensions were added in PGO 4.7 🎉

[yash-kalwani]

Both of these extensions were added in PGO 4.7 🎉

Hi @jkatz from what i understand timescaledb has two distribution licenses Apache 2 and TSL

So in version 4.7 the timescaledb version that is being used is of the Apache 2 license which limits the use of timescaledb in a database-as-a-service distribution ( which i am assuming what crunchydata is doing ) hence the 4.7 version of PGO only supports the Apache 2 license and not the TSL license right?

[jkatz]

This is covered in the 4.7 release notes and a blog post on the topic.