-
Notifications
You must be signed in to change notification settings - Fork 28
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 support for other ingress controller #113
Comments
Traefik already agreed on using ours, see https://twitter.com/timoreimann/status/1107792769421111296 |
I think with https://github.com/zalando-incubator/stackset-controller/releases/tag/v1.1.0 we enable anyone to create whatever resource to build the LB infrastructure. |
I thought about it again and realized, that we could pass the annotation name via flag, default to |
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Current the controller is tied to Skipper as an ingress controller and the dependency is for the traffic switching annotation. The controller should support other ingress providers as well such like Traefik which works exactly the same as skipper with the annotation
traefik.ingress.kubernetes.io/service-weights
. Nginx behaves a little differently because it doesn't define the multiple backends on the same ingress but allows multiple ingresses with the same host.The text was updated successfully, but these errors were encountered: