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.

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

ACL generation: Support multiple path matching per rule #813

Closed
tamalsaha opened this issue Jan 19, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@tamalsaha
Copy link
Member

commented Jan 19, 2018

From rigdon in Slack:

Hello! I'm working on converting a large-ish haproxy configuration to Voyager and everything is going very well so far. I have a question about the common way to convert some path-based routing though. Here is an example config

acl service_a_path path_beg -i /path1/subpath1
acl service_a_path path_beg -i /path1/subpath2
acl service_a_path path_beg -i /path2/subpath1

acl service_b_path path_beg -i /path1/subpath3
acl service_b_path path_beg -i /path2/subpath2
acl service_b_path hdr(host) -i serviceb.mydomain.com

use backend service_a if service_a_path
use backend service_b if service_b_path

This is a very small example but I have a double-digit number of backends with multiple host and path matching rules for each. Is there a sane way to configure a voyager ingress for this? I could add a path or host rule for each but that would result in a ton of duplication. Any help or advice at all would be appreciated. Thanks in advance!

@tamalsaha tamalsaha changed the title Support multiple path matching per rule ACL generation: Support multiple path matching per rule Jan 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.