-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
Hi!
As you have noticed I have started to contribute to this project. I am doing that because I am POCing a service mesh solution for Egnyte that is using this project.
To make it work, apart from #51 and #59, I would also need a few more features, so I would like to ask how do they align with your plans - perhaps you are already working on some of them or on the contrary: you will not even accept PRs with them. Let's have a chat about it. :)
So here it goes, in no specific order:
- Customizable HAproxy logs format
- Add custom config fragment to the upstream services frontends - mostly to capture some request headers for enriching the logs
- Add custom config fragment to the upstream services backends - for various things, like rspirep directives for example,
- Add a completely custom additional frontend(s) - where we would some custom logic above, f.e. splitting the traffic based on the paths between the upstream backends
- Listening on the UNIX sockets - as an alternative to above approach we could put the custom loginc into a separate HAproxy instance in front of the sidecar. To minimize the performance penalty we would like it to connect to the sidecar over these sockets.
- Custom load balancing algorithms? - maybe it doesn't make sense but we are looking for a way to make the load balancing as fair (even) as possible with the distributed load balancers..
So what do you think?
rushi47
Metadata
Metadata
Assignees
Labels
No labels