Marian Koreniuk 36b04218d7 test(kubernetes): assert where the hypervisor token is and where it is not ...

Every assert here was written against the mutation it exists for, and each was
checked to turn red on it and green without: putting the controller back in the
tenant, giving the tenant a non-empty config.clusters, pointing a sidecar at the
wrong kubeconfig, restoring the blanket toleration, hardcoding the driver's
default owner id, dropping capmox mode, and letting the controller ignore
proxmox.csi.enabled.

The negations carry `any: true`. Without it a negated containsDocument passes
whether or not the document is in the render.

Two of the cases are about objects rather than values: the tenant release must
carry no valuesFrom at all, and two clusters must derive different volume owner
ids. Both are properties a reader can check against the rendered output, which
is why they are asserted that way rather than by reading the templates.

Signed-off-by: Marian Koreniuk <moriarti@cp.if.ua>
Assisted-by: LLM

2026-09-29 21:04:05 +02:00

..

apps

test(kubernetes): assert where the hypervisor token is and where it is not

2026-09-29 21:04:05 +02:00

core

feat(kubernetes): add the Proxmox CSI driver, with its controller in this cluster

2026-09-29 21:04:05 +02:00

extra

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00

library

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00

system

feat(kubernetes): deploy the Proxmox cloud-controller-manager with the cluster

2026-09-29 21:04:05 +02:00

tests/cozy-lib-tests

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00