Skip to main content
Customer-Hosted Mixpeek supports qualified Kubernetes environments. The list is deliberately narrow and grows when a deployment asks it to, because every entry here is something we can run a qualification against and stand behind. “Runs on any Kubernetes” is a claim nobody can test, so we do not make it.

​
What a deployment requires

​
Qualification status

The table above is the configuration a deployment needs. This one is what a qualification establishes per environment. We keep these separate on purpose. A row here describes how a deployment on that distribution is established, which is a more useful answer than a version number.

​
Structural constraints

Two requirements are properties of the software rather than matrix results, so they hold everywhere:

​
Your Ray version is not an input

Mixpeek ships its own Ray, Python and CUDA userspace in one image, and the RayService it runs is ours. Whatever Ray you run elsewhere in the cluster has no bearing on whether Mixpeek works. That changes only for the shared-cluster integration, which is scoped per cluster. There the cluster is yours, so its runtime is an input, and that page says what it costs.

​
Getting a direct answer for your cluster

Ask Mixpeek to run the qualification suite against it. The report names the Kubernetes, KubeRay and storage configuration it found and whether each check passed on them. That is an answer about your cluster, which is worth more than a general claim about a matrix.
Compatibility results come from qualification runs rather than from a hand-maintained table, which is why this page sends you to a run against your own cluster instead of a list of version numbers.