Aleksei Sviridkin e894a26fcf test(e2e): add a GPUClaim suite on a fake extended resource ...

Nothing exercised GPUClaim end to end: ordering and binding, budget and
capacity refusals at admission, attachment to a VMI with the launcher
pod released from its scheduling gate onto the claim's node, the usage
record the claim owns, a template claim that waits for its tenant's
budget with its pod held at the gate and starts once the budget frees,
deletion of that claim with its VMI, and deletion of a tenant still
holding a claim. CI has no GPUs, so the suite advertises two units of a
fake extended resource on one node and restores the node at cleanup.

No device plugin serves the fake name, so virt-handler never hands the
guest a device and the VMI does not sync. The VM checks stop at what
admission, the controller and the scheduler decide; the guest side stays
manual.

The suite creates VMs on a VMDisk, so both VM application sources and
gpu-operator select it, and its install closure keeps gpu-operator.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-27 10:21:00 +03:00

..

chainsaw-test.yaml

test(e2e): add a GPUClaim suite on a fake extended resource

2026-10-27 10:21:00 +03:00