Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Creates and manages PostgreSQL clusters running in Kubernetes.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
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's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.
All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev
, variant.
In all other cases, including Chainguard Containers tagged as :latest
or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.
Although the -dev
container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev
variant into a more minimal production image.
To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl
, or API.
To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag 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 agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.