Last changed
docker pull cgr.dev/chainguard/postgres-operator
Need access to a specific version? Contact us.
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InCreates and manages PostgreSQL clusters running in Kubernetes.
The image is available on cgr.dev
:
The operator can be installed by using the provided
Helm chart which saves you the manual steps. The charts for both the Postgres Operator and its UI are hosted via the gh-pages
branch.
They only work only with Helm v3. Helm v2 support was dropped with v1.8.0.
Starting the operator may take a few seconds. Check if the operator pod is running before applying a Postgres cluster manifest.
If the operator doesn't get into Running
state, either check the latest K8s
events of the deployment or pod with kubectl describe
or inspect the operator
logs:
If the operator pod is running it listens to new events regarding postgresql
resources. Now, it's time to submit your first Postgres cluster manifest.
After the cluster manifest is submitted and passed the validation the operator
will create Service and Endpoint resources and a StatefulSet which spins up new
Pod(s) given the number of instances specified in the manifest. All resources
are named like the cluster. The database pods can be identified by their number
suffix, starting from -0
. They run the Spilo
container image by Zalando. As for the services and endpoints, there will be one
for the master pod and another one for all the replicas (-repl
suffix). Check
if all components are coming up. Use the label application=spilo
to filter and
list the label spilo-role
to see who is currently the master.
Open another CLI and connect to the database using e.g. the psql client.
When connecting with a manifest role like foo_user
user, read its password
from the K8s secret which was generated when creating acid-minimal-cluster
.
As non-encrypted connections are rejected by default set SSL mode to require
:
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement