HAProxy router fix for ip whitelist exceeding max config arguments that haproxy allows.#20357
Conversation
fixes bugz #1598738
|
/lgtm But... How much would it hurt performance (a) to use a file always and (b) to write the file using the template? Doing so could simplify the code, obviate the need for Edit: By "always", I mean for any positive number of whitelist entries, but not if there are zero entries. |
|
@Miciah yeah agree using a file always would be simpler. Bu it does come with a performance effect if a lot of routes use that annotation - does mean more IO + the processing is sequential so it makes for a slower startup. If there's not a lot of routes using that annotation, then it would be ok. |
|
LGTM |
|
/approve |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, Miciah, pravisankar, ramr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
Changes to use a file based acl if the annotation for the ip whitelist exceeds the max haproxy config line arguments.
fixes bugz #1598738
/cc @openshift/sig-network-edge