dusansusic / kubernetes-traefik Goto Github PK

View Code? Open in Web Editor NEW

64.0 64.0 35.0 76 KB

How to deploy Traefik Ingress Controller to K8S - DEPRECATED

kubernetes-traefik's People

Contributors

Stargazers

Watchers

kubernetes-traefik's Issues

Traefik Image version referenced in deployment.yaml , and Kubernetes support otdated

Your recipe provisions a Traefik v2..x
But you still use, in the configuration map, a traefik config, that is deprecated since traefik 1.7, this :

    [api]
    entryPoint = "traefik"

So I really do not understand. Is there a way to make your recipe actually work ?

Note the error message, very well reported in containous/traefik repo :

$ kubectl logs -f service/traefik-ingress-controller-http-service -n traefik
Found 2 pods, using pod/traefik-ingress-controller-7c9bb644cc-4jxgl
2020/05/09 13:39:38 command traefik error: field not found, node: entryPoint

secret tls namespace

Thanks for the tutorial. I'm working through a K8S setup for the first time and your documentation has been helpful.

I was getting an error that the secret traefik-ui-tls-cert could not be found. According to the docs:
"Secret API objects reside in a namespace. They can only be referenced by pods in that same namespace."

I adjusted the command to kubectl create secret tls traefik-ui-tls-cert --key k8s/ssl/tls.key --cert k8s/ssl/tls.crt --namespace traefik

Not getting an address

kubectl --namespace=traefik describe ingress traefik-dashboard-ingress
Name:             traefik-dashboard-ingress
Namespace:        traefik
Address:          
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host                    Path  Backends
  ----                    ----  --------
  traefik-ui.example.com  
                          /   traefik-dashboard:8080 (<none>)
Annotations:
  kubectl.kubernetes.io/last-applied-configuration:  {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{"kubernetes.io/ingress.class":"traefik","traefik.ingress.kubernetes.io/frontend-entry-points":"http,https","traefik.ingress.kubernetes.io/redirect-entry-point":"https","traefik.ingress.kubernetes.io/redirect-permanent":"true"},"name":"traefik-dashboard-ingress","namespace":"traefik"},"spec":{"rules":[{"host":"traefik-ui.example.com","http":{"paths":[{"backend":{"serviceName":"traefik-dashboard","servicePort":8080},"path":"/"}]}}]}}

  kubernetes.io/ingress.class:                          traefik
  traefik.ingress.kubernetes.io/frontend-entry-points:  http,https
  traefik.ingress.kubernetes.io/redirect-entry-point:   https
  traefik.ingress.kubernetes.io/redirect-permanent:     true
Events:                                                 <none>

Do we support subpath?

Is there a way we can have subpath but different backend in the traefik? We tested below but no luck.

backend:
serviceName: service-a
servicePort:80
path: /pathA
backend:
serviceName: service-b
servicePort:8000
path: /pathA/subPath

Does not work with :latest; field not found, node: entryPoint

Heya,

traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     Error               4          114s   10.32.0.3    kuber-03.local   <none>           <none>
traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     CrashLoopBackOff    4          116s   10.32.0.3    kuber-03.local   <none>           <none>
traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     Error               5          3m29s   10.32.0.3    kuber-03.local   <none>           <none>
traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     CrashLoopBackOff    5          3m31s   10.32.0.3    kuber-03.local   <none>           <none>
traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     Running             6          6m20s   10.32.0.3    kuber-03.local   <none>           <none>
traefik       traefik-ingress-controller-5d96649bb7-v5q4b   0/1     Error               6          6m21s   10.32.0.3    kuber-03.local   <none>           <none>

❯ k logs traefik-ingress-controller-5d96649bb7-v5q4b -n traefik
2020/04/06 21:01:45 command traefik error: field not found, node: entryPoint

To fix this, one must change

      - image: traefik

      - image: traefik:1.7

in kubernetes-traefik/deployment.yaml file.

Might be good idea to update that line.

Found some info on this particular error here traefik/traefik#5135

traefik https issue

After pushed deployment.yaml content,I am getting error.

Readiness probe failed: HTTP probe failed with statuscode: 404
Back-off restarting failed container

documentation error

Hi, I want to first thank you for sharing your work, and give a small contrib. :

I have noticed an error in the root README.md :
- You wrote :

Modify entryPoints.traefik.auth.basic section of deployment.yaml with new admin username/password

While you meant :

Modify entryPoints.traefik.auth.basic section of configmap.yaml with new admin username/password

Regards

dusansusic / kubernetes-traefik Goto Github PK

kubernetes-traefik's People

Contributors

Stargazers

Watchers

Forkers

kubernetes-traefik's Issues

Traefik Image version referenced in deployment.yaml , and Kubernetes support otdated

secret tls namespace

Not getting an address

Do we support subpath?

Does not work with :latest; field not found, node: entryPoint

traefik https issue

documentation error

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent