Fabian Stegemann ec3375c5c2 feat: expose Traefik LoadBalancer IP on Ingresses ... Configure Traefik to update the Ingress Resources `loadBalancer` status. This would provide users with at least following benefits: 1. It drastically simplifies the way one can quickly determine the relevant IP for a certain Ingress Resource, without the person deploying that Ingress needing to know how or where the LoadBalancer comes from. 2. Let's assume a User that has only permission to work in one specific namespace and is not allowed to *list* or *read* services from the `kube-system` namespace, for such a User this change would basically empower them to access the relevant information without being bottlenecked by another. 3. Allow tools like [external-dns](https://github.com/kubernetes-incubator/external-dns) to dynamically register all the available Ingress Resources with one of the Supported DNS Providers such as a local [CoreDNS](https://coredns.io).		2019-06-14 09:37:02 -07:00
..
coredns.yaml
traefik.yaml	feat: expose Traefik LoadBalancer IP on Ingresses	2019-06-14 09:37:02 -07:00