Use claimName field in the filestore location secret for repository server controller #2146
Conversation
This file contains 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
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
Signed-off-by: Rajat Gupta <rajat.gupta@veeam.com>
kale-amruta
changed the base branch from
AddUnitTests
to
repositoryServerUnitTestsChange
if podName and serviceName are not set even after the polling time exceeds
10 tasks
pavannd1
reviewed
Jul 13, 2023
PrasadG193
approved these changes
Jul 25, 2023
kale-amruta
force-pushed
the
fixfileStoreLocation
branch
from
89a3d81
to
a3070b1
Compare
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.
Change Overview
If filestore location storage is used as repository in repository server controller , claimName field in the location secret is not honoured. This field should be used to mount the pvc volume on repository server pod as a
kopia repository. This PR fixes the issue by adding pvc as volumes on the repository server podPull request type
Please check the type of change your PR introduces:
Issues
Test Plan