Using persistentVolume(Claims) with kube-api-test?

[skuzzle]

Hey,

I'm trying to test the Helm installation of my app using the kube-api-test module. The issue I'm facing is, that helm install always fails, logging messages like:

ready.go:284: 2025-05-02 12:05:36.342473 +0200 CEST m=+17.052392417 [debug] PersistentVolumeClaim is not bound: whatever-namespace/pvc-name

So naturally, I tried to create the required PVs (and StorageClass) before running helm install, but the PVs are stuck in Pending state and hence the PVCs are also stuck in Pending.
Here is a similar issue filed for kwok, where creating the StorageClass and PV upfront apparently does solve the problem.

Now I'm curious whether I'm missing something or whether this just fundamentally doesn't work with the kube-api-test approach?

[manusa]

kube-api-test doesn't run controllers, so it's likely that you won't be able to test some scenarios.

In Eclipse JKube we do have some integration tests that rely on kube-api-server, maybe you want to take a look:

https://github.com/eclipse-jkube/jkube/blob/96b2b3882b2c03c297882795586e68c3e1d2f4a6/jkube-kit/helm/src/test/java/org/eclipse/jkube/kit/resource/helm/HelmServiceInstallIT.java

If your charts are more complex, I'd recommend you to switch to test containers or any other solution which allows you to perform the test with a real or semi-real cluster.