crunchy-postgres-vectorchord

Container images for Crunchy Postgres for Kubernetes with the VectorChord extension installed.

Two images are published for each release:

Both cover linux/amd64 and linux/arm64.

docker pull ghcr.io/aaronspruit/crunchy-postgres-vectorchord:18-1.1.1

<cdpg> is the Crunchy image tag and <vchord> is the VectorChord version. Every tag moves to the newest matching build. Pin a digest for a reference that never moves.

Postgres 15, 16, 17 and 18 are built. That is the set of majors Crunchy supports.

versions.yaml lists the combinations that are built. Crunchy publishes the pg_upgrade image for the newest Postgres major alone, so the upgrade image exists for that major only.

apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
spec:
  (...)
  config:
    parameters:
      shared_preload_libraries: "vchord.so"

apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
spec:
  (...)
  patroni:
    dynamicConfiguration:
      postgresql:
        parameters:
          shared_preload_libraries: "vchord.so"

apiVersion: v1
kind: ConfigMap
metadata:
  name: enable-vchord
data:
  init.sql: |-
    \c mydatabasename
    CREATE EXTENSION IF NOT EXISTS vchord CASCADE;
---
apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
spec:
  (...)
  databaseInitSQL:
    name: enable-vchord
    key: init.sql

Pass CDPG_TAG and VECTORCHORD_TAG to build the database image:

docker build . \
  --build-arg CDPG_TAG=ubi9-18.4-2621 \
  --build-arg VECTORCHORD_TAG=1.1.1

Add CDPG_IMAGE to build the pg_upgrade image:

docker build . \
  --build-arg CDPG_IMAGE=crunchy-upgrade \
  --build-arg CDPG_TAG=ubi9-18.4-2621 \
  --build-arg VECTORCHORD_TAG=1.1.1

The Crunchy registry needs no account. It issues a token to an anonymous caller.

I shamelessly took a lot of code from cloudnative-vectorchord and from budimanjojo/crunchy-postgres-vectorchord.