viirya opened a new pull request, #15: URL: https://github.com/apache/spark-connect-gateway/pull/15
### 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 `gateway` crate — the binary entry point that wires all the previously imported layers into a runnable server. It reads the YAML config (`--config`, default `config.yaml`), builds the chosen backend pool (static or Kubernetes service-watch) and affinity store (in-memory or Redis), installs the configured authenticator, tenant resolver, rate limiter, and audit sink, wraps the pool in active health probing, starts the admin HTTP server for metrics and health endpoints, and serves the Spark Connect gRPC surface through the proxy. `gateway` depends on all 14 other crates in the workspace, so it lands last of the code PRs and closes the dependency graph. With this PR the workspace `members` list is complete (15 crates) and `cargo build --workspace` produces a runnable `gateway` binary. Only the docs/deploy PR (Dockerfile, Helm chart, examples, docs, full README) remains after this one. ### 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 — the binary is new, and nothing shipped previously. ### 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 (204 tests pass, 10 Redis/testcontainer tests `#[ignore]`). The built binary runs: `gateway --help` prints its CLI. ### 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]
