From ec3375c5c267773f34f3dc33650e03cd5e237a40 Mon Sep 17 00:00:00 2001 From: Fabian Stegemann Date: Sat, 1 Jun 2019 19:45:43 +0200 Subject: [PATCH] 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). --- manifests/traefik.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/manifests/traefik.yaml b/manifests/traefik.yaml index fa2d56641fe..c256820392a 100644 --- a/manifests/traefik.yaml +++ b/manifests/traefik.yaml @@ -8,3 +8,4 @@ spec: set: rbac.enabled: "true" ssl.enabled: "true" + kubernetes.ingressEndpoint.useDefaultPublishedService: "true"