[ocp4_workload_external_odf] Set storageClassName when OCP version > 4.17 #9618
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 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.
SUMMARY
Version 4.19 doesn't obey the "disableStorageClass" and is creating the storage class, causing issues on the labs. Setting a different name to the storageClassName, allows create our own storageClass (and set as default). This PR is to set only when is a newer version of OCP, as in previous versions this change is causing issues with noobaa pvc (it creates with the SC name defined, which doesn't exist because old versions doesnt create the SC)
ISSUE TYPE
COMPONENT NAME
ocp4_workload_external_odf role