Chainguard Container for REPO_NAME

Minimal container image for running Kubernetes conformance tests

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/REPO_NAME:latest

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

Compatibility Notes

This image is compatible with the official Kubernetes conformance tests and can be used as a drop-in replacement for registry.k8s.io/conformance:latest. It runs the same conformance test suite and supports the same environment variables for configuration.

Getting Started

To run the conformance tests on your Kubernetes cluster, you can create a job with the following configuration:

# First create a service account with appropriate permissions
apiVersion: v1
kind: ServiceAccount
metadata:
  name: conformance-serviceaccount
  namespace: default
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: conformance-serviceaccount-cluster-admin
subjects:
- kind: ServiceAccount
  name: conformance-serviceaccount
  namespace: default
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io
---
# Then create the conformance test job
apiVersion: batch/v1
kind: Job
metadata:
  name: kube-conformance
  namespace: default
spec:
  template:
    spec:
      serviceAccountName: conformance-serviceaccount
      containers:
      - name: kube-conformance
        image: cgr.dev/chainguard/kube-conformance:latest
        env:
        - name: E2E_FOCUS
          value: "\\[Conformance\\]"
        - name: E2E_PARALLEL
          value: "1"
        - name: E2E_PROVIDER
          value: "local"
        - name: E2E_VERBOSITY
          value: "4"
        - name: RESULTS_DIR
          value: "/tmp/results"
        volumeMounts:
        - name: results
          mountPath: /tmp/results
      volumes:
      - name: results
        emptyDir: {}
      restartPolicy: Never
  backoffLimit: 0

The kube-conformance image can also be used with Sonobuoy, which is a diagnostic tool that makes it easier to run the Kubernetes conformance tests:

# Install sonobuoy CLI
sonobuoy run --sonobuoy-image cgr.dev/chainguard/sonobuoy:latest --plugin-env=e2e.E2E_FOCUS="[Conformance]" --kube-conformance-image cgr.dev/chainguard/kube-conformance:latest

# Wait for completion
sonobuoy status

# Get results
outdir=$(sonobuoy retrieve)
sonobuoy results $outdir

Documentation and Resources

The conformance tests can be configured with the following environment variables:

• E2E_FOCUS: Test filter to select which tests to run (default: \[Conformance\])
• E2E_PARALLEL: Number of tests to run in parallel (default: 1)
• E2E_PROVIDER: Kubernetes provider for the tests (default: local)
• E2E_SKIP: Tests to skip (default: none)
• E2E_VERBOSITY: Verbosity level for the tests (default: 4)
• KUBECONFIG: Path to kubeconfig file (defaults to in-cluster config)
• RESULTS_DIR: Directory to store test results (default: /tmp/results)

Additional resources:

• Kubernetes Conformance Tests Documentation
• Sonobuoy Documentation
• Kubernetes Conformance Program
• Certified Kubernetes Conformance Program

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.