BlueAPI can use persistent volumes as a scratch area. This allows the user to retain different environments for different versions of BlueAPI, and to avoid problems related to the shared file system such as permission issues.
:::{seealso} Configure the Application :::
The relevant configuration is below:
:language: yaml
With both initContainer.enabled and initContainer.persistentVolume.enabled to true, BlueAPI will create or attempt to bind to an existing Persistent Volume Claim, which when fulfilled will be used as a scratch area.
BlueAPI can reuse existing PVCs by setting initContainer.persistentVolume.existingClaimName. When this is not set it defaults to scratch-<blueapi-version>. meaning the same Persistent Volume is reused when installing the same version of BlueAPI in a given namespace.
This can be set to any value to create and reuse arbitrarily named PVs.
The easiest way to interact with the created persistent volume is via the Kubernetes plugin for VSCode. This is documented here.