Add Persistent Volume Support for LocalDisk ArmorProfileModel Data #243
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
Resolves data accessibility issues in multi-replica manager deployments by adding persistent volume (PV) support for LocalDisk-type
ArmorProfileModel
objects, enabling data sharing across manager instances.Key Features Added
behaviorModeling.usePersistentVolume
Helm value to toggle PV usage for LocalDisk-typeArmorProfileModel
datapersistentVolume
settings with configurable PVC claim name (varmor-manager-apmdata-pvc
)emptyDir
volume as default storage option/var/log/varmor/apmdata
across instancesBenefits
ArmorProfileModel
dataArmorProfileModel
import/export operations across manager restartsemptyDir
limitsNotes
varmor-manager-apmdata-pvc
in the manager namespace before enablingusePersistentVolume
emptyDir
remains default with a 500Mi size limit for lightweight deployments