Skip to content

Update cross-cluster networking article with notes#428

Open
Khushbu-Parekh wants to merge 1 commit into
MicrosoftDocs:mainfrom
Khushbu-Parekh:patch-1
Open

Update cross-cluster networking article with notes#428
Khushbu-Parekh wants to merge 1 commit into
MicrosoftDocs:mainfrom
Khushbu-Parekh:patch-1

Conversation

@Khushbu-Parekh
Copy link
Copy Markdown
Contributor

Added note about cross-cluster networking availability and limitations.

Added note about cross-cluster networking availability and limitations.
@prmerger-automator
Copy link
Copy Markdown
Contributor

@Khushbu-Parekh : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit b83639b:

✅ Validation status: passed

File Status Preview URL Details
articles/kubernetes-fleet/howto-configure-use-cross-cluster-networking.md ✅Succeeded

For more details, please refer to the build report.

@Khushbu-Parekh
Copy link
Copy Markdown
Contributor Author

#Sign-off

@prmerger-automator
Copy link
Copy Markdown
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @sjwaight

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Azure Kubernetes Fleet Manager cross-cluster networking how-to by adding a callout note that clarifies current regional availability and sets expectations about broader availability.

Changes:

  • Added a NOTE callout listing the Azure regions where cross-cluster networking is currently available.
  • Added a statement about expected timeline for global availability.

@Court72
Copy link
Copy Markdown
Contributor

Court72 commented May 22, 2026

@sjwaight

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants