Adding GKE support for Managed Lustre#4022
Merged
Merged
Conversation
tpdownes
approved these changes
May 1, 2025
1 task
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.
One feature that was missing from the new managed lustre module was adding gke-support for creating the module and for setting up VMs to accept gke-compatible lustre instances.
Note that this will also require an update to slurm-gcp as certain directories are mounted prior to any startup scripts running.
This was tested by running two blueprints
gke_support_enabled: trueand the other withgke_support_enabled: false