-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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 label matching for kubernetes ingests #363
Comments
Any thoughts on this? |
Hi @pnegahdar, sorry for the delay :) |
re: annotation vs labels I think that the way that k8s sees the distiction is:
I think labels is the way to go for this use case, as it would allow us to request the subset of ingresses we want from the apiserver without having to get them all and then filter client side. |
I agree and seems like the kubernetes docs agree too: http://kubernetes.io/docs/user-guide/annotations/ |
You're right, I read the doc too quickly :) Let's go on labels ! |
@pnegahdar is this something that you are still working on? |
Actually scheduled doing it today and tomorrow. Hoping to make the 1.0 cut. |
@pnegahdar unless you already have some work in progress on this, I am thinking of picking this one up sometime next week... |
@errm Wrote a starting implementation. A bit stuck on how to unit test sanely -- kubernetes has a somewhat complex label selector syntax (http://kubernetes.io/docs/user-guide/labels/) that is somewhat hard to effectively mock out. |
Will this be included in an upcoming release? |
I want to add label (or annotation) matching to kubernetes. i.e
traefik --web --kubernetes --kubernetes.label-filter "traefik/balancer-name=load-balancer-1"
would then ensure only those with that label join the balancer.See: http://kubernetes.io/docs/user-guide/labels/#label-selectors
I know namespaces are currently supported but thats not fine-grained enough for most kube deploy systems. Thoughts on this?
The text was updated successfully, but these errors were encountered: