[testing-on-gke] fix custom csi driver build #28
Merged
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.
fix(testing-on-gke): Ensure correct gcsfuse source for CSI driver build
Refactored the
run-gke-tests.shscript to accurately managegcsfuseandgcsfuse-toolssource code. This introduces separate configurations for their respective repositories, including distinct environment variables for source directories, branches, and force update flags.This change is crucial as it ensures the custom GCSFuse CSI driver is built using the binary from the specified
gcsfuse_src_dirand its corresponding branch, rather than incorrectly using paths related togcsfuse-tools. This rectifies the build process for the custom driver, leading to more reliable GKE tests with the intended GCSFuse version.b/420533841