Tested versions¶

The adapter supports exactly this set. It is the set the design was checked against and the set the kind test suite runs.

Kueue is needed only in Kueue mode, and its group-version is checked only then. In plain mode, Kueue may be absent; if it is installed, it must not manage jobs that name no queue.

The tests run on kind, on a cluster of one control-plane node and two workers, with each component installed from a manifest kept in the repository (internal/kindtest/testdata/manifests) and cmd/dispatch-admission deployed in it. They run go/dispatch's backend conformance suite against the adapter in both modes, and cluster cases of the adapter's own. Run the conformance suite against kind says how to run them and what each case checks.

What preflight checks, and what it cannot¶

At Factory, the adapter refuses a cluster that does not serve the group-versions in the table above, with ErrUnsupported. It cannot read the controllers' versions. A namespace user cannot read the Trainer, JobSet or Kueue deployments, so the matrix is documented and tested rather than detected. A different release that serves the same group-versions is not refused, and is not tested.

Other versions in the build¶

The test cluster's kind.yaml pins no node image, so the suite runs whatever node image the kind binary defaults to.

Where the cluster must give image volumes¶

The default publish route uses an image volume, which is on by default in Kubernetes 1.37 and needs no configuration there. Clusters below 1.35, or a container runtime that mounts image volumes noexec, need the init container route. See Mount the publish image.