Status: Accepted (constraint from both tracks) · Date: 2026-07
Mirantis' k0rdent AI provides the infrastructure substrate (clusters, OS, CUDA,
GPUs) in the broader AI Cloud picture. The enterprise team's MVP must install
on a customer's existing single server / cluster, and enterprise buyers will
bring EKS/AKS/GKE/OpenShift/k0s — anything conformant.
Token Factory assumes only a conformant Kubernetes cluster with schedulable
GPUs (NVIDIA GPU Operator present, or installable as an optional chart
dependency). No component may require k0rdent APIs, CRDs, or tooling.
- Hard requirement from the enterprise MVP ("cannot depend on k0rdentAI").
- Widens the addressable market to every k8s distribution — including
NeoClouds that standardize on something else.
- Keeps the team boundary clean: cluster lifecycle is the k0rdent AI team's
product; tokens are ours. Where both are sold together, k0rdent provisions
the cluster and Token Factory installs onto it — composition, not coupling.
- The umbrella chart owns everything above the cluster line: namespaces, GPU
resource requests, storage classes as values, ingress as values.
- CI must test against at least one non-Mirantis distribution (kind + GPU
operator mock for logic; a real GPU cluster for e2e).
- Multi-cluster orchestration in the NeoCloud edition is done by our
control plane (regions), not by cluster-management tooling.
Clarified after the first k0rdent AI ↔ Token Factory alignment (see
the layer below):
- The working assumption for the NeoCloud is that Token Factory deploys
as one tenant of k0rdent AI's Kubernetes-as-a-service — consuming the
cluster it hands us exactly like any other conformant Kubernetes. That is
composition on top of this ADR, not a violation of it.
- Edition-specific k0rdent integrations are permitted: the IREN/NeoCloud
packaging may add optional k0rdent-aware capabilities (dedicated-cluster
provisioning, bench-capacity signals). Per the editions model these are
packaged into that edition; the baseline stack stays vanilla-k8s-only, and
the enterprise edition never requires k0rdent.