do we have cookie based routing for httpproxy?

projectcontour / contour

Contour is a Kubernetes ingress controller using Envoy proxy.

https://projectcontour.io

Apache License 2.0

3.71k stars 672 forks source link

do we have cookie based routing for httpproxy? #6510

Closed chatwithruben closed 2 weeks ago

chatwithruben commented 3 months ago

What question do you have?: i have a use case where httpproxy should validate the cookie contents and route to particular service accordinly.

cookie name is "cookie" inside cookie we have something like X-Service-version-v12 also in some cookies it might be X-Service-version-v13

so what we wanted is our httpproxy should be capable of reading for the cookie and route to particular service accordingly.

github-actions[bot] commented 3 months ago

Hey @chatwithruben! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace

sunjayBhatia commented 3 months ago

Contour does not have cookie based request matching at this time, but we do support cookie based load balancing/session affinity to enable you to maintain a stateful session to an individual app instance, see the RequestHash or Cookie load balancing strategies documented here: https://projectcontour.io/docs/1.29/config/request-routing/#load-balancing-strategy

chatwithruben commented 3 months ago

@sunjayBhatia Can we consider this as a a good use case?

github-actions[bot] commented 1 month ago

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

After 60d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

Mark this Issue as fresh by commenting
Close this Issue
Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

github-actions[bot] commented 2 weeks ago

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

After 60d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

Mark this Issue as fresh by commenting
Close this Issue
Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack