【问题标题】:Kubernetes:Traefik (v2.2) dashboard returning "404 page not found"Kubernetes:Traefik (v2.2) 仪表板返回“404 page not found”
【发布时间】:2020-10-29 18:40:26
【问题描述】:

在 Kubernetes 环境中调出 Traefik 仪表盘时遇到问题,以下是我的 traefik 部署设置:

kind: Deployment
apiVersion: apps/v1
metadata:
  namespace: ingress-traefik
  name: traefik
  labels:
    app: traefik

spec:
  replicas: 1
  selector:
    matchLabels:
      app: traefik
  template:
    metadata:
      labels:
        app: traefik
    spec:
      serviceAccountName: traefik-ingress-controller
      containers:
        - name: traefik
          image: traefik:v2.2
          ports:
            - name: web
              containerPort: 80
            - name: websecure
              containerPort: 443
            - name: admin
              containerPort: 8080
          args:
            - --api
            - --api.dashboard=true
            - --providers.kubernetesingress
            - --providers.kubernetescrd
            - --entrypoints.web.Address=:80
            - --entrypoints.websecure.Address=:443
            - --ping.entryPoint=web
            - --log.level=debug

以及仪表板 ingressRoute 设置:

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: traefik-dashboard
  namespace: ingress-traefik
spec:
  entryPoints:
    - web
    - websecure
  routes:
  - match: Host(`traefik.example.io`) && (PathPrefix(`/api`) || PathPrefix(`/dashboard`))
    kind: Rule
    services:
    - name: api@internal
      kind: TraefikService
  tls:
    secretName: cert-stage-wildcard
    domains:
      - main: example.io
        sans:
          - "*.example.io"

当 curl 仪表板站点返回“404”时:

$ curl -v https://traefik.example.io/dashboard
*   Trying 159.203.52.215:443...
* TCP_NODELAY set
* Connected to traefik.example.io (159.203.52.215) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /home/ken.tsoi/anaconda3/ssl/cacert.pem
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=*.example.io
*  start date: Oct 28 16:10:10 2020 GMT
*  expire date: Jan 26 16:10:10 2021 GMT
*  subjectAltName: host "traefik.example.io" matched cert's "*.example.io"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET /dashboard HTTP/1.1
> Host: traefik.example.io
> User-Agent: curl/7.68.0
> Accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Thu, 29 Oct 2020 17:51:07 GMT
< Content-Length: 19
< 
404 page not found
* Connection #0 to host traefik.example.io left intact

查看 traefik 的日志,执行“curl”时没有看到任何更新,但是,执行“grep dashboard”确实看到仪表板 ingressRoute 已配置:

time="2020-10-29T17:26:53Z" level=debug msg="Configuration received from provider kubernetescrd: {\"http\":{\"routers\":{\"ingress-traefik-traefik-dashboard-e1cd6df5083c9bc8083c\":{\"entryPoints\":[\"web\",\"websecure\"],\"service\":\"api@internal\",\"rule\":\"Host(`traefik.example.io`) \\u0026\\u0026 (PathPrefix(`/api`) || PathPrefix(`/dashboard`))\",\"tls\":{\"domains\":[{\"main\":\"example.io\",\"sans\":[\"*.example.io\"]}]}}},\"middlewares\":{\"ingress-traefik-traefikbasicauth\":{\"basicAuth\":{\"users\":[\"testuser:$apr1$sS2w2/sx$aw4f8LNSyypdknEUOqcIp/\"],\"realm\":\"Traefik\"}}}},\"tcp\":{},\"udp\":{},\"tls\":{}}" providerName=kubernetescrd
time="2020-10-29T17:26:53Z" level=debug msg="Added outgoing tracing middleware api@internal" middlewareType=TracingForwarder entryPointName=web routerName=ingress-traefik-traefik-dashboard-e1cd6df5083c9bc8083c@kubernetescrd middlewareName=tracing 

(顺便说一句:我已经使用 basicAuth 进行身份验证,它正在工作,所以我从 ingressRoute 中省略了它)

谁能指出可能是什么问题?

【问题讨论】:

  • 我遇到了同样的问题。当我尝试打开带有尾随 / 的仪表板时,问题消失了,在您的示例中,它将如下所示:https://traefik.example.io/dashboard/
  • 感谢@nOnvme 的启发,我实际上已经自己解决了这个问题。请在此处查看:stackoverflow.com/questions/64582491/…。关键是,我设置了api.insecure=true,这样我就可以在本地调出dashboard,然后像其他服务一样做路由。
  • 您好,@KenTsoi 很高兴您找到了问题的解决方案。我鼓励您在这里提供您的答案,以便为未来的读者更好地了解。
  • 谢谢@DawidKruk,我已经添加了答案。

标签: kubernetes traefik traefik-ingress


【解决方案1】:

此问题已解决(不确定这是解决方案还是解决方法):

请在此处查看:https://stackoverflow.com/a/64709491/6716204

关键是,我设置了api.insecure=true,这样我就可以在本地调出dashboard,然后像其他服务一样做路由。

【讨论】:

  • 更具体:在问题 YAML 的 args 部分下,添加一个新命令:“--api.insecure=true”。为我工作,谢谢。
猜你喜欢
  • 2017-06-08
  • 1970-01-01
  • 2020-12-05
  • 2022-01-01
  • 2016-03-16
  • 2011-11-09
  • 1970-01-01
  • 1970-01-01
  • 2021-12-21
相关资源
最近更新 更多