Obtaining Registry Access

This guide explains how to locate and pull Fluss artifacts from the Ververica registry, including Docker images, Helm charts, and Java client JARs. It is intended for operators and developers who have completed the initial credentialing setup described in the Ververica Platform registry access guide and are ready to deploy Fluss.

Overview

The Ververica distribution of Fluss is available from the same private registry and uses the same credential workflow as Ververica Platform.

To request credentials, log in to the Helm OCI registry, and create a Kubernetes image pull secret, complete the steps outlined in the foundational guide: Ververica Platform - Chart Repository and Image Access.

The Helm charts are public — no credentials are needed to pull them.

his manual is limited to the Fluss-specific information: which artifact paths to pull and where to find the Java client JARs. Pull-secret wiring, registry-access verification, and image-pull troubleshooting are covered in Deploying Fluss on Kubernetes.

Fluss Artifacts Endpoints

All Fluss artifacts share the host registry.ververica.cloud. Only the Docker image requires credentials (issued by Ververica Customer Support); the Helm charts and the Java client JARs are public.

Most operators deploy the all-in-one fluss-bundle chart. The standalone fluss chart is for environments where you bring your own ZooKeeper cluster.

Because Ververica Platform pulls the image from this registry, the image pull secret you create for Fluss must be also referenced under zookeeper.image.pullSecrets. For detailed instructions on this setup, see Deploying Fluss on Kubernetes.

Logging In

Authentication is only needed for the Docker images. The Helm charts are public and pull without login.

Set your credentials as environment variables for the snippet below:

1export REGISTRY_USERNAME="<REGISTRY_USERNAME>"
2export REGISTRY_PASSWORD="<REGISTRY_PASSWORD>"

Helm OCI registry (public)

The Helm charts in platform-charts are public: OCI-based charts need no helm repo add and no helm registry login. Pull or install them directly. For example:

1helm pull oci://registry.ververica.cloud/platform-charts/fluss-bundle --version 0.9.1-vv-2

Docker

Set the image credential pair (issued by Ververica Customer Support) and log in to pull Fluss images locally:

1export REGISTRY_USERNAME="<REGISTRY_USERNAME>"
2export REGISTRY_PASSWORD="<REGISTRY_PASSWORD>"
3docker login registry.ververica.cloud \
4  --username "$REGISTRY_USERNAME" \
5  --password "$REGISTRY_PASSWORD"

For Kubernetes pods to pull Fluss images, you must create a namespace-scoped image pull secret instead of running docker login.

To complete this setup, see the Ververica Platform guide linked above and the Create the Image Pull Secret section of the deployment manual.

Java Client JARs

If you write Java applications that link against the Fluss client library, you can obtain JAR files from a public JFrog repository without using Ververica Platform credentials. Ververica Platform publishes two Maven group IDs:

• org.apache.fluss:* - Fluss core artifacts, which include the client API, runtime, and connector base.
• com.ververica.fluss:* - Ververica Platform plugin installer artifacts.

The Ververica plugin installer (see Installing Fluss) uses this repository as its default Maven source when resolving plugin coordinates. Operators do not need to configure a private Maven settings file unless they are pulling plugins from an alternate mirror.

Further Reading

• Ververica Platform — chart repository and image access — foundational credential and login workflow shared with VVP
• Apache Fluss Documentation — upstream reference
• Fluss Helm Chart Documentation — complete reference for all fluss: values

Related manuals:

• Deploying Fluss on Kubernetes
• Installing Fluss
• Configuring Remote Storage
• Securing Fluss
• Configuring Prometheus Monitoring
• Configuring Lake Tiering
• Reading and Writing Fluss
• Lake Job Credentials
• Fluss Helm Chart - Additional Notes