-
Notifications
You must be signed in to change notification settings - Fork 117
Add support for http header routing #1222
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.
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
base: main
Are you sure you want to change the base?
Conversation
b1b19ad
to
f63b75a
Compare
d8bfab6
to
a54ef74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this PR ready to review?
@erich23 is there any update regarding this? |
I have something that works with basic header routing locally, but I think the community needs something that's on-par with CNCF project standards: #1177 (comment). Unfortunately, I don't have the bandwidth to deliver something that meets the listed requirements. |
tableMemory.store
now holds a list of*httpv1alpha1.HTTPScaledObject
When routing, iterate through list of
*httpv1alpha1.HTTPScaledObject
and match the headers based on passed in http headers. Here are the rules:HTTPScaledObject.spec.Headers
HTTPScaledObject
which specifies no.spec.Headers
, fail routing.Checklist
README.md
docs/
directoryFixes #