docs: update EPP protocol spec with streaming mode and health check requirements#2514
docs: update EPP protocol spec with streaming mode and health check requirements#2514Neha-dot-Yadav wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Neha-dot-Yadav The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @Neha-dot-Yadav! |
|
Hi @Neha-dot-Yadav. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/assign @danehans |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This PR updates the Endpoint Picker Protocol (EPP) specification document to include two previously undocumented requirements:
Streaming Mode Support: Documents that the EPP MUST support streaming mode for inference requests and responses, enabling full-duplex communication for real-time AI inference workloads.
Health Checking: Documents the gRPC health checking protocol implementation, including:
These features are already implemented in the codebase (see
cmd/epp/runner/health.goandpkg/epp/handlers/server.go) but were missing from the protocol specification document. This PR brings the documentation in sync with the actual implementation.Which issue(s) this PR fixes:
Fixes #994
Does this PR introduce a user-facing change?: