Chainguard Container for apache-kvrocks

Apache Kvrocks is a distributed key-value database. Apache Kvrocks uses RocksDB as its storage engine and is compatible with Redis protocol.

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/apache-kvrocks:latest

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

Compatibility Notes

Chaingaurd's Apache Kvrocks container image is comparable to the Kvrocks image maintained by Apache. Like most other Chainguard container images, the Apache Kvrocks image contains only the dependencies it needs to function, and doesn't include things like a shell or package manager.

Getting Started

You can start the container with Docker by starting the image and exposing port 6666 - such as:

  docker run -d --name exporter \
  -p 6666:6666 \
  cgr.dev/ORGANIZATION/apache-kvrocks:latest

Next, use redis-cli or valkey-cli command to connect to the kvrocks server. This example will set a key named samplekey to the value examplevalue:

redis-cli -p 6666 SET samplekey examplevalue

To ensure the database is working correctly, test that you can retrieve the value you just set:

redis-cli -p 6666 GET samplekey

Using with kvrocks-operator

This image can be used with the kvrocks-operator.

First, deploy the operator by following these instructions from the Kvrocks GitHub repository.

Next, deploy kruise:

helm repo add openkruise https://openkruise.github.io/charts/
helm repo update
helm install kruise openkruise/kruise

Following that, deploy the kvrocks CRDs and operator:

helm repo add kvrocks-operator https://rockslabs.github.io/kvrocks-operator
helm install kvrocks-crd kvrocks-operator/kvrocks-crd -n kvrocks
helm install kvrocks-operator kvrocks-operator/kvrocks-operator -n kvrocks

Finally, deploy an instance of a kvrocks cluster, by providing a KVRocks manifest like the following:

apiVersion: kvrocks.apache.org/v1alpha1
kind: KVRocks
metadata:
  name: kvrocks-test
spec:
  image: cgr.dev/ORGANIZATION/apache-kvrocks:latest
  imagePullPolicy: IfNotPresent
  master: 1
  replicas: 3
  password: "..."
  # ...

Replace # ... with the remaining setup of your specification, including settings for kvrocksConfig field as well as any other fields. Please refer to the standard.yaml manifest for an example definition of a kvrocks cluster.

Documentation & Resources

Please refer to the upstream documentation for more details about Apache Kvrocks.

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.