Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GEP: Percentage-Based Request Mirroring #3171

Open
jakebennert opened this issue Jun 21, 2024 · 2 comments · May be fixed by #3508
Open

GEP: Percentage-Based Request Mirroring #3171

jakebennert opened this issue Jun 21, 2024 · 2 comments · May be fixed by #3508
Labels
kind/gep PRs related to Gateway Enhancement Proposal(GEP)
Milestone
v1.2.0

Comments

@jakebennert
Copy link
Contributor

What would you like added:
I'd like to add an enhancement to the existing feature HTTP request mirroring. Right now Request Mirroring is an all or nothing feature. Either 100% of request are mirrored, or 0% are. Percentage-Based Request Mirroring will allow users to specify a percentage of requests they'd like mirrored as opposed to every single request.

This feature is already supported by Envoy, and should be supportable by HAProxy and NGINX.

Why this is needed:
This feature is already supported by Envoy, so adding it for the Gateway API would enable better integration between the two products. There's also an existing user desire for this feature on the HAProxy side and NGINX side. Since Request Mirroring is already supported by the Gateway API, Percentage-Based Request Mirroring would a clear improvement on this pre-existing feature.
@robscott robscott added the kind/gep PRs related to Gateway Enhancement Proposal(GEP) label Jul 1, 2024
@robscott robscott added this to the v1.2.0 milestone Jul 1, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 29, 2024
@youngnick
Copy link
Contributor

/remove-lifecycle stale

This one has moved to Experimental in 1.2.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 30, 2024
@LiorLieberman LiorLieberman linked a pull request Dec 17, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/gep PRs related to Gateway Enhancement Proposal(GEP)
Projects
None yet
Milestone
v1.2.0
Development

Successfully merging a pull request may close this issue.

conformance tests for percentage-based request mirroring LiorLieberman/gateway-api
5 participants
@robscott @youngnick @k8s-ci-robot @jakebennert @k8s-triage-robot