Support full duplex streaming in body-based routing extension

[rramkumar1]

Ref: #321

I updated the unit test in request_test.go but I owe unit tests for the changes in server.go and also updates to the integration test.

Will send a separate PR for that.

[k8s-ci-robot]

Hi @rramkumar1. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	aa6139d
🔍 Latest deploy log	https://app.netlify.com/sites/gateway-api-inference-extension/deploys/67daf07cacce2600094b2f18
😎 Deploy Preview	https://deploy-preview-463--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rramkumar1]

/assign @kfswain
/assign @ahg-g

[kfswain]

/lgtm
/hold

I think this works, but we might want to refactor this a tad to try to bring the Send() logic into the same place. Author's disgression.

[ahg-g]

/ok-to-test

[hzxuzhonghu]

As envoy documents, all http headers are normalized ti lowercase, not sure the extproc bypas that or not.

[kfswain]

I think we can significantly simplify BBR, but I dont think it needs to block this PR. @rramkumar1 can you spin up some issues for that?
I think we can:

• Remove k8s logic
• cleanup full duplex logic
• Document how this would hook into an OSS GW(the expectation is that this extension would run before any HTTP routing is done, we should have an example of that via the EnvoyPatchPolicy or an OSS GW implementation doing that)
• add a bit more testing

Otherwise I think this PR is mergable

[rramkumar1]

I think we can significantly simplify BBR, but I dont think it needs to block this PR. @rramkumar1 can you spin up some issues for that? I think we can:

• Remove k8s logic
• cleanup full duplex logic
• Document how this would hook into an OSS GW(the expectation is that this extension would run before any HTTP routing is done, we should have an example of that via the EnvoyPatchPolicy or an OSS GW implementation doing that)
• add a bit more testing

Otherwise I think this PR is mergable

Filed #535 for removing the k8s dependency
Have #443 that is already tracking addition testing
Filed #536 for adding usage examples

In terms of cleanup, let's follow-up offline on that so we can discuss how we want things to look.

[kfswain]

In terms of cleanup, let's follow-up offline on that so we can discuss how we want things to look.
SG, I'm cleaning up EPP streaming as well.

/lgtm
Thanks!

[rramkumar1]

/retest

[kfswain]

/unhold

[kfswain]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kfswain, rramkumar1

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kfswain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment