docs: Fix broken NCCL test anchor links for GKE blueprints

[Grimreaper00025]

Description

The NCCL test documentation link in cloud.google.com/ai-hypercomputer/docs/create/gke-ai-hypercompute#deploy-run-nccl-tas-test is obsolete and leads to a broken or missing anchor tag on the generic page. The underlying Cloud Docs have been split into hardware-specific anchors on https://docs.cloud.google.com/ai-hypercomputer/docs/nccl/test-gke.

While the develop branch has already successfully updated this endpoint for the A3 Mega blueprint, the remaining blueprints were missed and were still routing to the dead /create/ link.

This PR aligns the remainder of the GKE blueprints to point sequentially to their new hardware-specific anchors in the nccl/test-gke docs (e.g., #a3-ultra, #a4, #a4x).

Affected Files

• examples/gke-a3-ultragpu/README.md
• examples/gke-a4/README.md
• examples/gke-a4x/README.md
• examples/gke-consumption-options/dws-calendar.md

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 addresses broken documentation links related to NCCL testing in various GKE blueprints. By redirecting these links to the updated, hardware-specific documentation pages, the changes ensure that users are directed to the correct resources for running NCCL tests on their respective cluster configurations.

Highlights

• Documentation Update: Updated obsolete NCCL test documentation links across multiple GKE blueprint README files.
• Anchor Alignment: Corrected broken anchor tags by pointing them to the new hardware-specific documentation pages for A3 Ultra, A4, and A4X configurations.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the NCCL test documentation links across several GKE example README files. The review feedback recommends using the standard public domain 'cloud.google.com' instead of 'docs.cloud.google.com' to maintain consistency and prevent potential authentication or layout issues for external users.

[parulbajaj01]

@Grimreaper00025 Let's apply the gemini suggestions.

[parulbajaj01]

LGTM!