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

Add plugin hook for adding new load balancing algorithms #11336

Open
airhorns opened this issue May 1, 2024 · 2 comments · May be fixed by #11381
Open

Add plugin hook for adding new load balancing algorithms #11336

airhorns opened this issue May 1, 2024 · 2 comments · May be fixed by #11381
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@airhorns
Copy link

airhorns commented May 1, 2024

Currently, it doesn't seem possible for a plugin to extend the available load balancing algorithms that can be used. Instead, operators needs to fork, rebuild and deploy the project, or ninja-mount lua files, overwriting source code at runtime, both of which seems error prone and hard.

But, there's lots of interest in new or different load balancing algorithms for ingress-nginx, a lot of which haven't made it into the core. #9239 and #9025 are both attempts to add new algorithms that could have been plugins. Personally, I have all sorts of weird ideas I want to try for my own load balancing problems, and I'm also aware of several different private initiatives that do the same.

It'd be great if we could add new implementations to the list of available implementations, and then access all annotations inside a plugin to power it.

And finally, for bonus points, its really hard to test plugins outside this repo, it'd be really great to improve support for that as well.

@airhorns airhorns added the kind/feature Categorizes issue or PR as related to a new feature. label May 1, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 1, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link

github-actions bot commented Jun 1, 2024

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants