-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Traefik does not update the kubernetes ingress status or address #3377
Comments
Hello @r0fls! Thank you so much for your interest in traefik! The functionality of traefik to update ingress status was added via #3324. This feature will be available on traefik version 1.7. If you want to try out the feature with an experimental build, you can use the Thanks! |
@dtomcej Looks that one piece is missing in your change. The RBAC needs to be extended to update the ingress. https://github.com/containous/traefik/blob/master/examples/k8s/traefik-rbac.yaml needs: - apiGroups:
- extensions
resources:
- ingresses/status
verbs:
- update |
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: traefik-ingress-controller
rules:
[...]
- apiGroups:
- extensions
resources:
- ingresses/status
verbs:
- update |
Thx, markdown ate my yaml ;) |
The example ClusterRole needs to updated for Træfik 1.7 to allow updating the status after successfully provisioning the Ingress. /closes traefik#3377 (cherry picked from commit 99fa7c7729c9e99545fb12f3cf80785a17096cdc)
Closed by #4397. |
This comment has been minimized.
This comment has been minimized.
Just got this working now. For anyone else wondering, you need to use the command line arguments (or equivalent config settings) to get this working.
|
Bug
What did you do?
I deployed the [stable/traefik] helm chart to a 1.8.9 kubernetes cluster in AWS. I added the annotation
service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
to the resulting traefik service, so that it creates an external load balancer (this may not be needed in your cluster). I then deployed a basic hello world deployment/svc/ingress with the traefik ingress class set. If I manually retrieve the hostname of the traefik service ELB,kubectl get svc traefik-test -o yaml | grep -A 3 status
(assuming the deployment was namedtraefik-test
), then curl it with the host header set to my ingress hostname, then I see the hello world app:So, things work up to there.
What did you expect to see?
Status of my ingress should be filled in with the ELB from the traefik controller. For example, a similar ingress fulfilled by the nginx ingress controller shows:
What did you see instead?
Traefik does not set the ingress status of the fulfilled ingress, or address (a field in
kubectl get ing <INGRESS_NAME>
), which means it won't play nicely with things like external-dns:Output of
traefik version
: (What version of Traefik are you using?)I tried the version specified in the [stable/traefik] helm chart (1.5.4) and the latest recommended version by traefik, 1.6.2.
What is your environment & configuration (arguments, toml, provider, platform, ...)?
I'm using the [stable/traefik] controller with no relevant modifications. The only modification was the one made to the service annotations.
The text was updated successfully, but these errors were encountered: