This repository was archived by the owner on Jul 14, 2026. It is now read-only.
take storageclass for operator from single parameter - #22
Open
boddumanohar wants to merge 1 commit into
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently to set storage class for all the stateful resources within the operator we need to set them at 4 places:
this way.
the first 2 are needed for the operator's own stateful set resources:
this PR eliminates the need for setting these 2 parameters
To idea is to have a single storage class for all the operator managed PVCs. At the moment, if the default storage class cannot be used we override the storage class parameter at
We don't expect customers to use to use different storage class for each of them.