Skip to content

feat(global-router): deploy and validate discovery-backed global ingress - #17278

Draft
sachalmalick wants to merge 1 commit into
codex/global-router-rr-backendsfrom
codex/global-router-rr-rollout
Draft

sachalmalick wants to merge 1 commit into
codex/global-router-rr-backendsfrom
codex/global-router-rr-rollout

Conversation

@sachalmalick

Copy link
Copy Markdown
Contributor

Summary

Closes #17275. Stack part 3, after #17276 and #17277.

Add a runtime Dockerfile, Kubernetes renderer, operator-model configuration example, and a functional validation client for Global Ingress plus GDS. Each cluster runs one private HTTP ingress and one GDS reading locally imported MCS EndpointSlices. Model identity is configured; frontend and router addresses/readiness remain dynamic. GDS receives read-only EndpointSlice access; ingress has no Kubernetes token.

The deployed test uses real Dynamo Frontends, CPU Mockers, and Relays. It validates HTTP round robin; Global Ingress does not yet receive Relay load/KV state streams. Services remain private, with no additional compute provisioned.

Validation

  • 75 targeted Rust tests passed; local runtime-container smoke passed eight unary/SSE chat/completion requests with an exact 2/2/2/2 pool split.
  • Four regional GDS services each discovered four routers and four pools through MCS; every advertised router was reachable from each region.
  • Two steady-state runs: 320/320 successful inference requests, exactly 10 to each pool from each region per run; half SSE, half unary.
  • Replaced one regional frontend: every GDS learned its new address and removed the old address. All eight GDS/ingress pod UIDs and restart counts remained unchanged.
  • Existing eight reserved GPU instances and 30 protected pods retained their identities and healthy state.
  • Initial startup run also returned 160/160 HTTP 200s; one ingress observed membership propagation mid-run. Validation now waits for a stable discovery inventory before checking exact balance.
  • Python compilation, Black, isort, Ruff, Flake8, docs lint, strict CODEOWNERS and whitespace checks passed.

The initial runtime-container test caught a builder/runtime libc mismatch; the validated image uses Ubuntu 24.04 to match the builder.

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

@github-actions github-actions Bot added feat documentation Improvements or additions to documentation labels Oct 25, 2026

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

Labels

documentation Improvements or additions to documentation feat size/XL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant