Container Image & Binary

Conformance EE is distributed through Kubermatic’s enterprise OCI registry. Since it is a private repository, all artifacts are obtained using the kubermatic-ee-downloader tool or by pulling the container image with valid registry credentials.

Access requires a valid Kubermatic Enterprise Edition subscription. Contact our solutions team for access.

Downloading the Binary

The kubermatic-ee-downloader CLI tool downloads the conformance-tester binary from the OCI registry and saves it locally. This is the recommended way to obtain the binary for local or TUI-based usage.

Getting kubermatic-ee-downloader

Download the appropriate binary for your platform from the kubermatic-ee-downloader releases:

PlatformArchitectureBinary
Linuxamd64kubermatic-downloader_linux_amd64
Linuxarm64kubermatic-downloader_linux_arm64
macOSamd64kubermatic-downloader_darwin_amd64
macOSarm64kubermatic-downloader_darwin_arm64
Windowsamd64kubermatic-downloader_windows_amd64
Windowsarm64kubermatic-downloader_windows_arm64

Authentication

Credentials are resolved in the following order:

  1. CLI flags--username and --password
  2. Docker config~/.docker/config.json (e.g., after docker login)
  3. Interactive prompt — if credentials are still missing, the tool asks on stdin

Download the Conformance Tester

List available tools:

kubermatic-ee-downloader list

Example output:

TOOL               VERSIONS    OS                      ARCH        DESCRIPTION
conformance-tester latest-cli linux,darwin,windows    amd64,arm64 Kubermatic conformance cli

Download the conformance-tester binary:

kubermatic-ee-downloader get conformance-tester

Download a specific version to a custom directory:

kubermatic-ee-downloader get conformance-tester \
  --version v1.2.0 \
  --output /usr/local/bin

With explicit registry credentials:

kubermatic-ee-downloader get conformance-tester \
  --username <your-username> \
  --password <your-password>

CLI Reference

FlagShortDescription
--username-uRegistry username
--password-pRegistry password
--verbose-vEnable verbose logging
--version-VTool version (default: tool-specific or “latest”)
--archTarget architecture (e.g. amd64, arm64)
--osTarget operating system (e.g. linux, darwin, windows)
--registry-rOverride OCI registry (default: tool’s registry)
--output-oOutput directory (default: .)
--output-oOutput directory (default: .)

Container Image

For in-cluster deployment (e.g., running as a Kubernetes Job), the container image is available at:

quay.io/kubermatic/conformance-ee

Pull with Docker using your registry credentials:

docker login quay.io
docker pull quay.io/kubermatic/conformance-ee:latest

Tags

TagDescription
latestLatest release
v*Specific version (e.g., v1.0.0)