Ververica Platform Docker Images

Using the Ververica Platform public registry

For convenience, Ververica hosts a public authenticated Docker registry that contains images of all Ververica Platform components.

The registry is hosted at registry.platform.data-artisans.net, and the images are namespaced by the minor version of the release. For example the 1.3.4 release would exist under v1.3 like so:

registry.platform.data-artisans.net/v1.3/appmanager:1.3.4
registry.platform.data-artisans.net/v1.3/flink:1.6.0-dap1-scala_2.11

Attention

The registry hosted by Ververica is provided without SLA. If you require availability guarantees, you should import the Ververica Platform images into your own registry.

Note

In order to access these images, you will need to authenticate with the registry. Depending on how your Kubernetes environment is configured will determine which approach is best for your scenario. For more details on how to achieve this, please consult these official Kubernetes documentation pages on Add ImagePullSecrets to a service account, Using a Private Registry, and Pull an Image from a Private Registry.

Using a private registry

If you wish to host the Ververica Platform images yourself, you will have to pull, re-tag, and push the images accordingly. Below is a snippet showing one approach to make this easier, updating REGISTRY and IMAGE respectively to suit your case.

$ REGISTRY=registry.acme.inc; \
   IMAGE=v1.3/appmanager:1.3.4; \
   docker pull registry.platform.data-artisans.net/${IMAGE} && \
   docker tag registry.platform.data-artisans.net/${IMAGE} ${REGISTRY}/${IMAGE} && \
   docker push ${REGISTRY}/${IMAGE}

Note

These snippets are provided as examples, and may need to be adapted for your particular operating system/environment.

Using an offline registry

If you’re using a private registry that has restricted network access, you may need to be able to fetch the images, move them, and then load them into the target registry. Below is a simple recipe which builds on the one above to accomplish this.

$ REGISTRY=registry.acme.inc; \
   IMAGE=v1.3/appmanager:1.3.4; \
   ARCHIVE=$(echo ${IMAGE} | sed -e 's/.*\///g' -e 's/:/-/g').tar.gz; \
   docker pull registry.platform.data-artisans.net/${IMAGE} && \
   docker tag registry.platform.data-artisans.net/${IMAGE} ${REGISTRY}/${IMAGE} && \
   docker save ${REGISTRY}/${IMAGE} | gzip > ${ARCHIVE}

$ REGISTRY=registry.acme.inc; \
   IMAGE=v1.3/appmanager:1.3.4; \
   ARCHIVE=$(echo ${IMAGE} | sed -e 's/.*\///g' -e 's/:/-/g').tar.gz; \
   gunzip -c ${ARCHIVE} | docker load && \
   docker push ${REGISTRY}/${IMAGE}

Note

These snippets are provided as examples, and may need to be adapted for your particular operating system/environment.