fix(k8s): share one PVC across multi-role ExApp Deployments#97
Merged
oleksandr-nc merged 1 commit intomainfrom Apr 14, 2026
Merged
fix(k8s): share one PVC across multi-role ExApp Deployments#97oleksandr-nc merged 1 commit intomainfrom
oleksandr-nc merged 1 commit intomainfrom
Conversation
Signed-off-by: Oleksander Piskun <oleksandr2088@icloud.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When a K8s ExApp declares multiple
<k8s-service-roles>, HaRP was creating a separate PVC per role (nc-app-{name}-{role}-data) and mounting each at a role-suffixed path. But AppAPI setsAPP_PERSISTENT_STORAGE=/nc_app_{appId}_data- no role suffix, so the ExApp would write to a path that didn't match the PVC mountpoint.This makes the PVC role-agnostic by dropping
role_suffixfromexapp_container_volume. All roles of one ExApp now share a single PVC mounted at the same path asAPP_PERSISTENT_STORAGE. Deployment names stay per-role so each role still gets its own Deployment/pod/selector. PVC labels also switched to role-agnostic ones (part-of,name,component=exapp-data) since the PVC is no longer tied to a specific role.Note: if anyone had a multi-role ExApp deployed with the pre-patch build, the old per-role PVCs will orphan after this goes in. They're empty (that's literally the bug), so there's no data to lose — just
kubectl delete pvcthe old names if you care about cleanup.