Image Overview: cass-config-builder

• Overview
• Details
• Tags History
• Provenance

Minimal cass-config-builder container image.

Download this Image

The image is available on cgr.dev:

docker pull cgr.dev/chainguard/cass-config-builder:latest

To use this image you can follow up the official documentation of installing the Helm Chart for K8ssandra Operator, here.

In the ImageConfiguration section which allows you to configure the K8ssandra images to use custom registries or custom images, you can use the the this image for the cass-config-builder image config, here as an example:

apiVersion: config.k8ssandra.io/v1beta1
kind: ImageConfig
metadata:
  name: image-config
images:
...
  config-builder: "cgr.dev/chainguard/cass-config-builder:latest"
...

If you do this change right after your installation, you might need to delete the pods under the k8ssandra-operator namespace for the changes to take effect by the pods being recreated but please verify that the pods are up and running before proceeding with the next steps.

Next, to test the image whether it is actually working you should create K8ssandraCluster CR with the following spec, here:

apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  name: demo
  namespace: k8ssandra-operator
spec:
  cassandra:
    serverVersion: "4.0.1"
    datacenters:
      - metadata:
          name: dc1
        size: 3
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: standard # make sure that you configure this to match your environment
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
        config:
          jvmOptions:
            heapSize: 512M
        stargate:
          size: 1
          heapSize: 256M

After you created the K8ssandraCluster CR, there should be a pod with the name demo-dc1-default-sts-0 under the k8ssandra-operator namespace up and running because the cass-config-builder image is going to be used as an initContainer so if the pod is up and running we can confirm that the image is working as expected.