这是indexloc提供的服务，不要输入任何密码
Skip to content

Add Managed Lustre support in gke-a4 #4654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Sep 24, 2025
Merged

Add Managed Lustre support in gke-a4 #4654

merged 1 commit into from
Sep 24, 2025

Conversation

@parulbajaj01
Copy link
Contributor

@parulbajaj01 parulbajaj01 commented Sep 15, 2025

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

  • Fork your PR branch from the Toolkit "develop" branch (not main)
  • Test all changes with pre-commit in a local branch #
  • Confirm that "make tests" passes all tests
  • Add or modify unit tests to cover code changes
  • Ensure that unit test coverage remains above 80%
  • Update all applicable documentation
  • Follow Cluster Toolkit Contribution guidelines #

@parulbajaj01 parulbajaj01 requested review from a team and samskillman as code owners September 15, 2025 10:22
@parulbajaj01 parulbajaj01 added the release-improvements Added to release notes under the "Improvements" heading. label Sep 15, 2025
bytetwin
bytetwin reviewed Sep 15, 2025
View reviewed changes
Copy link
Collaborator

@bytetwin bytetwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given there are too many changes, I prefer to have a seperate blueprint eg) gke-a4-lustre.yaml with gke-a4 readme explaining what this blueprint is about.

And readme of managed lustre module referencing this as an example on how to use managed lustre. This can be a seperate PR

samskillman
samskillman requested changes Sep 23, 2025
View reviewed changes
Copy link
Collaborator

@samskillman samskillman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also please comment on what manual tests were performed.

@parulbajaj01
Copy link
Contributor Author

parulbajaj01 commented Sep 23, 2025

Manual testing steps performed:

  1. Deployed the GKE A4 cluster with Managed-Lustre enabled.
  2. Checked if the PVC is bound to the PV: kubectl get pvc
  3. Mounted the PVC in a pod, which will mount the Managed-Lustre file system.
  4. Checked if the pod is running and the volume is mounted: kubectl get pod
  5. Wait for the pod to be in the 'Running' state
  6. Exec into the pod: kubectl exec -it -- /bin/sh
  7. Inside the pod, checked the mount:
    df -h /mnt/lustre
    mount | grep lustre
  8. Managed-Lustre file system was mounted at /mnt/lustre and was able to read/write data to this path from within the container.

samskillman
samskillman previously approved these changes Sep 23, 2025
View reviewed changes
@parulbajaj01 parulbajaj01 merged commit e281a88 into GoogleCloudPlatform:develop Sep 24, 2025
12 of 63 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vikramvs-gg vikramvs-gg vikramvs-gg approved these changes

@samskillman samskillman samskillman left review comments

@bytetwin bytetwin Awaiting requested review from bytetwin

Assignees

No one assigned

Labels

release-improvements Added to release notes under the "Improvements" heading.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@parulbajaj01 @samskillman @bytetwin @vikramvs-gg