viirya opened a new pull request, #13:
URL: https://github.com/apache/spark-connect-gateway/pull/13

   ### What changes were proposed in this pull request?
   
   Part of importing the Spark Connect Gateway reference implementation into
   `apache/spark-connect-gateway` as a series of small, bottom-up PRs (tracked 
in
   the do-not-merge reference PR #1).
   
   This adds the `scg-pool-k8s` crate — a Kubernetes service-watch backend 
`Pool`.
   It watches a `Service`'s `Endpoints` object in a given namespace and exposes 
the
   ready endpoints as the routing backend set, so the gateway's backend 
membership
   tracks the Spark Connect pods dynamically. This is the dynamic counterpart to
   the fixed-membership `scg-pool-static`.
   
   `scg-pool-k8s` depends on the `scg-routing` crate whose `Pool` trait it
   implements, and pulls in the kube / k8s-openapi client stack. It is imported 
as
   its own PR (rather than grouped) because of that larger dependency surface. 
It
   compiles and tests on its own (unit tests plus a router integration test) 
and is
   appended to the workspace `members` list. It is consumed later by the 
`gateway`
   binary.
   
   ### Why are the changes needed?
   
   Implements the reference gateway from the approved SPIP (SPARK-58455), 
imported
   one reviewable piece at a time.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   `cargo fmt --all --check`, `cargo clippy --workspace --all-targets -- -D 
warnings`,
   `cargo build --workspace`, and `cargo test --workspace` all pass locally.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Yes, co-authored with Claude Code.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to