cid 0c8342e845bd8adbb108a8874d9c6ac503cdd6970911bf46782b8fd3fb701b65 · original · open access · via openalex
Title: DRACheck: Stateful Testing and Durable Allocation Semantics for Kubernetes Dynamic Resource Allocation (software artifact) Authors: Hsiu-Chi Tsai Venue: Zenodo (CERN European Organization for Nuclear Research) Year: 2026 Canonical: doi:10.5281/zenodo.21798596 URL: https://doi.org/10.5281/zenodo.21798596 Collector: openalex OA: true ABSTRACT DRACheck is a stateful testing framework for the Kubernetes Dynamic Resource Allocation (DRA) structured allocator. It drives pinned upstream allocator code with deterministically generated stateful operation traces and checks counter conservation against a separate allocation-time ledger, reproducing a "committed-counter resurrection" failure class: a mutable ResourceSlice inventory update can make still-committed capacity appear free, so the scheduler admits a device that over-commits a shared counter. This archive is the software artifact accompanying the preprint "No Capacity Resurrection: Stateful Testing and Durable Allocation Semantics for Kubernetes Dynamic Resource Allocation" (Hsiu-Chi Tsai); it is source code only — the manuscript itself is not included here, as it is published as an arXiv preprint of the same title (see the related identifiers). It contains: the tester and its campaigns (fuzz, differential across allocator variants, decision-preserving and intent-preserving replay, delta-debugging, and a bounded model check); an allocator-path footprint prototype (a fork of the pinned upstream allocator) that reads committed charges from allocation-time state rather than mutable inventory; the vendored dependencies for a fully offline, hermetic build (Go 1.26, GOPROXY=off); a one-command reproduction script (reproduce.sh); the recorded campaign outputs; and a SHA-256 manifest (MANIFEST.sha256). Reproduction: extract, then run ./reproduce.sh with Go 1.26+ (the build is offline via vendor/). Integrity: sha256sum -c MANIFEST.sha256. The real apiserver/etcd durability modes are skipped automatically when envtest control-plane binaries are absent, so the rest of the run still completes. Scope: quantitative results are author-reported and should not be interpreted as independently reproduced; see the preprint's Artifact Availability statement.