Make Backend configuration more flexible #1
Conversation
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
ErmakovDmitriy
force-pushed
the
backend-volumes
branch
from
40abd60 to
c896979
Compare
jekabs-karklins
approved these changes
May 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR introduces support for optional Persistent Volume Claim or Backend helm chart which solves 2 potential issues:
/home/node/app/uploads/in a containerHow Has This Been Tested
The changed Helm chart was deployed on OKD 4.17 (RedHat Openshift Upstream) with restricted SecurityContext.
The introduction of the Volume in
/home/node/app/uploads/fixed the Backend startup problem.Docs Updated