Repository navigation
feat(global-router): deploy and validate discovery-backed global ingress - #17278
Draft
sachalmalick wants to merge 1 commit into
Draft
sachalmalick wants to merge 1 commit into
sachalmalick wants to merge 1 commit into
Conversation
Signed-off-by: Sachal Malick <s@chal.ai>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
The initial runtime-container test caught a builder/runtime libc mismatch; the validated image uses Ubuntu 24.04 to match the builder.