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
GLBC ingress: only handle annotated ingress #59
Comments
such an annotation already exists ("kubernetes.io/ingress.class"), or maybe I'm confused? |
@bprashanth , thanks for the link. I somehow missed the documentation on |
Yeah that makes sense, I'm guessing you mean --ingress-class=gce only handles ingresses with |
- if flag == "voyager", the you only handle ingress that has voyager annotation - if flag == "", then handle no annotaion or voyager annotation ref: - kubernetes/ingress-nginx#59
This issue was moved to kubernetes/ingress-gce#20 |
* Rename monitor.lua module to statsd.monitor.lua * Rename statsd.monitor.lua to statsd_monitor.lua
Hi,
We are running a HAProxy based ingress in our clusters. But for a few service, we would like to run GLBC ingress. I did not see any way to tell ingress controllers, which Ingress resource they can handle. Can Ingress controllers can only handle ingress that has a specific annotation applied to it (similar to how schedulers do it):
"ingress.alpha.kubernetes.io/controller": glbc
Here is a way I could see being implemented. Glbc controller adds a new flag --ingress-controller.
If --ingress-controller flag value is empty, then glbc should handle any Ingress that has no annotation "ingress.alpha.kubernetes.io/controller" or annotation set to "" string.
If --ingress-controller flag is not empty, then only handle Ingress that has
"ingress.alpha.kubernetes.io/controller" : "".
Thanks.
The text was updated successfully, but these errors were encountered: