Skip to content

feat(global-router): resolve MCS pool models and live frontends - #17276

Draft
sachalmalick wants to merge 1 commit into
global-router-v2from
codex/global-router-mcs-routing-metadata
Draft

sachalmalick wants to merge 1 commit into
global-router-v2from
codex/global-router-mcs-routing-metadata

Conversation

@sachalmalick

Copy link
Copy Markdown
Contributor

Summary

Closes #17275 (discovery metadata prerequisite).

Global Ingress polls /pools, but the MCS backend previously returned no model or frontend addresses. Add optional --routing-config model/location bindings and join them with ready imported frontend EndpointSlices by source cluster, namespace, and DGD name. Frontend addresses remain dynamic; a ready Relay is still required for pool membership. Existing constructors and unconfigured behavior remain compatible.

This is the first PR in a stack; the deployment and validation example follows separately.

Validation

  • 75 targeted tests passed across global-discovery-client, global-discovery-service, global-router, and global-ingress.
  • Added coverage for frontend replacement/readiness, Relay withdrawal, identity isolation, IPv6 URLs, and invalid configuration.
  • Targeted Rust formatting, diff whitespace, and strict changed-file CODEOWNERS checks passed.

@copy-pr-bot

copy-pr-bot Bot commented Oct 25, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

This branch has not been deployed

No deployments
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.

1 participant