k3s/manifests/traefik.yaml

apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz
  set:
    rbac.enabled: "true"
    ssl.enabled: "true"
    metrics.prometheus.enabled: "true"
    kubernetes.ingressEndpoint.useDefaultPublishedService: "true"
Switch to wrangler-api and helm-controller 2019-05-26 06:42:09 +00:00			`apiVersion: helm.cattle.io/v1`
Add traefik ingress controller 2019-02-08 04:16:02 +00:00			`kind: HelmChart`
			`metadata:`
			`name: traefik`
			`namespace: kube-system`
			`spec:`
bump traefik version to 1.7.14 (#769) * bump traefik version 2019-08-29 03:21:07 +00:00			`chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz`
Fix ingress 2019-02-12 18:08:26 +00:00			`set:`
			`rbac.enabled: "true"`
			`ssl.enabled: "true"`
Enable metrics endpoint to Traefik 2019-08-22 22:03:42 +00:00			`metrics.prometheus.enabled: "true"`
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-01 17:45:43 +00:00			`kubernetes.ingressEndpoint.useDefaultPublishedService: "true"`