Chainguard Container for verticadb-operator-fips

The VerticaDB operator automates tasks and monitors the state of your Vertica on Kubernetes deployments.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/verticadb-operator-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's VerticaDB Operator FIPS container image is comparable to the VerticaDB Operator from Vertica. Chainguard's version is a minimal, secure, and regularly updated container image designed to run Java applications. It leverages the security features of Chainguard Images, including low-to-zero CVEs, automated nightly builds, high-quality SBOMs, verifiable signatures, and reproducible builds.

Getting Started

For production scenarios, it's recommended you follow Vertica's guide on deploying Vertica DB operator using the official Helm chart.

To illustrate how this image works, the following is an example of how to deploy VerticaDB Operator locally.

Start by creating a values.yaml file:

cat <<EOF > values.yaml
image:
  repo: cgr.dev
  name: ORGANIZATION/verticadb-operator-fips:latest
EOF

Then add the repository for Vertica Charts:

helm repo add vertica-charts https://vertica.github.io/charts
helm repo update

Next, install the Helm chart for VerticaDB Operator:

helm install vdb-op --wait --namespace my-verticadb-operator --create-namespace vertica-charts/verticadb-operator

This will deploy VerticaDB Operator on your local Kubernetes cluster. Now you can install VerticaDB by creating a VerticaDB custom resource (CR):

 cat << EOF > vdb.yaml
apiVersion: vertica.com/v1beta1
kind: VerticaDB
metadata:
  name: verticadb-sample
spec:
  annotations:
    VERTICA_MEMDEBUG: “2”  # Required if running macOS with an arm based chip
  communal:
    path: "/communal/vertica-db-tutorial"
    includeUIDInPath: true
  subclusters:
    - name: sc
  volumes:
  - name: hostpath
    hostPath:
      path: /tmp
  volumeMounts:
  - name: hostpath
    mountPath: /communal
EOF

kubectl apply --namespace my-verticadb-operator -f vdb.yaml

Wait for the VerticaDB instance to be initialized:

kubectl wait --for=condition=DBInitialized=True --namespace my-verticadb-operator vdb/verticadb-sample --timeout=10m

Check the status of the VerticaDB instance:

kubectl get pods --namespace my-verticadb-operator --selector app.kubernetes.io/instance=verticadb-sample

NAME                                   READY   STATUS              RESTARTS   AGE
verticadb-sample-sc-0                  1/1     ContainerCreating   0          97s
verticadb-sample-sc-1                  1/1     ContainerCreating   0          97s
verticadb-sample-sc-2                  1/1     ContainerCreating   0          97s

You can now access the VerticaDB instance using the vsql client:

kubectl exec -it --namespace my-verticadb-operator verticadb-sample-sc-0 -- vsql

This will open a vsql shell where you can run SQL commands.

Documentation and Resources

• VerticaDB Operator Helm Charts
• Official VerticaDB Operator documentation

What are Chainguard Containers?

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:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

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.

Need additional packages?

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.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

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.