Skip to content

managed-luster updating zone from us-central1-c to us-central1-a - #5811

Merged
siddhartha-quad merged 1 commit into
GoogleCloudPlatform:developfrom
sriram-quad:zonalupdate
Jun 22, 2026
Merged

managed-luster updating zone from us-central1-c to us-central1-a#5811
siddhartha-quad merged 1 commit into
GoogleCloudPlatform:developfrom
sriram-quad:zonalupdate

Conversation

@sriram-quad

@sriram-quad sriram-quad commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

The enough resources available to fulfill the request in us-central1-c got exhausted and changed to us-central1-a zone

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 #

@sriram-quad
sriram-quad requested a review from a team as a code owner June 19, 2026 09:35
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modifies the configuration for the GKE managed Lustre daily test suite. The change shifts the target deployment zone to us-central1-a, likely to align with infrastructure availability or testing requirements.

Highlights

  • Zone Configuration Update: Updated the deployment zone for the GKE managed Lustre daily test from us-central1-c to us-central1-a.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@google-cla

google-cla Bot commented Jun 19, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@github-actions github-actions Bot added the external PR from external contributor label Jun 19, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the zone for the gke-managed-lustre daily test from us-central1-c to us-central1-a. The reviewer recommends also updating the corresponding example blueprint (examples/gke-managed-lustre.yaml) to use us-central1-a to maintain consistency and ensure the example remains functional.

Comment thread tools/cloud-build/daily-tests/tests/gke-managed-lustre.yml
@sriram-quad
sriram-quad force-pushed the zonalupdate branch 2 times, most recently from edfc63a to e0eb930 Compare June 19, 2026 09:53
@aslam-quad

Copy link
Copy Markdown
Contributor

/gcbrun

@aslam-quad aslam-quad added the release-chore To not include into release notes label Jun 19, 2026
@aslam-quad
aslam-quad requested a review from LAVEEN June 19, 2026 09:54

@rahimkhan19 rahimkhan19 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@aslam-quad

Copy link
Copy Markdown
Contributor

/gcbrun

@siddhartha-quad
siddhartha-quad merged commit d8d70ac into GoogleCloudPlatform:develop Jun 22, 2026
13 of 82 checks passed
ep-nag pushed a commit to nagconsulting/cluster-toolkit that referenced this pull request Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external PR from external contributor release-chore To not include into release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants