Traefik Ingress 中的重定向過多

Question

我正在嘗試在 Kubernetes 中將 Traefik 設置為我的應用程序的負載均衡器。 我能夠在 Minikube 上成功設置它，但在生產中情況略有不同。

使用一些網絡策略，流量通過我們組織的 PLB 進入，我想到達 Traefik。 根據規則，它應該重定向到相應的服務。

我可以使用以下配置查看 Traefik 儀表板，但我在 abc.com/ms/whoami 上的 whoami 上收到了太多重定向

基礎設施： Orgs PLB > Traefik LB > 基於角色的路由 > 微服務 A/B/C...

部分配置

traefik.yaml

---
apiVersion: v1
kind: Service
metadata:
  name: traefik
spec:
  type: LoadBalancer
  selector:
    app: traefik
  ports:
    - protocol: TCP
      port: 80
      name: web
      targetPort: 80
    - protocol: TCP
      port: 443
      name: websecure
      targetPort: 80
    - protocol: TCP
      port: 8080
      name: admin
      targetPort: 8080
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: traefik-dashboard
spec:
  tls: {}
  entryPoints:
    - web
    - websecure  
  routes:
  - match: Host(`traefik-abc.com`) && (PathPrefix(`/services/traefik`) || PathPrefix(`/api`))
    kind: Rule
    services:
    - name: api@internal
      kind: TraefikService
    middlewares: 
      - name: basic-auth
        name: stripprefix-traefik
---  
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: traefik-abc.com
  annotations:
    kubernetes.io/ingress.class: "org.plb"
spec:
  backend:
    serviceName: traefik
    servicePort: 8080
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: abc.com
  annotations:
    kubernetes.io/ingress.class: "org.plb"
spec:
  backend:
    serviceName: traefik
    servicePort: 80

whoami.yaml

kind: Deployment
apiVersion: apps/v1
metadata:
  name: whoami
  labels:
    app: whoami
spec:
  replicas: 1
  selector:
    matchLabels:
      app: whoami
  template:
    metadata:
      labels:
        app: whoami
    spec:
      containers:
        - name: whoami
          image: containous/whoami
          ports:
            - name: web
              containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: whoami
spec:
  ports:
    - protocol: TCP
      name: web
      port: 80
  selector:
    app: whoami
---  
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: whoami
spec:
  tls: {}
  entryPoints:
    - web
    - websecure
  routes:
  - match: Host(`abc.com`) && PathPrefix(`/ms/whoami`)
    kind: Rule
    services:
    - name: whoami
      port: 80

日志

- - [13/Aug/2020:23:56:09 +0000] "GET /ms/whoami HTTP/1.1" 301 17 "-" "-" 114 "web-to-websecure@internal" "-" 0ms
- - [13/Aug/2020:23:56:09 +0000] "GET /ms/whoami HTTP/1.1" 301 17 "-" "-" 115 "web-to-websecure@internal" "-" 0ms
- - [13/Aug/2020:23:56:09 +0000] "GET /ms/whoami HTTP/1.1" 301 17 "-" "-" 116 "web-to-websecure@internal" "-" 0ms
.....
.....
- - [13/Aug/2020:23:56:09 +0000] "GET /ms/whoami HTTP/1.1" 301 17 "-" "-" 128 "web-to-websecure@internal" "-" 0ms

Answer 1

我也會關注客戶端上的日志。 可能是您的 whoami 應用程序從/ms/whoami重定向到/ms/whoami/ ，然后您的外部負載均衡器從/ms/whoami/重定向到/ms/whoami 。

或者可能是您的應用程序/微服務從/ms/whoami重定向到/之類的其他內容，然后您的負載均衡器將其重定向回/ms/whoami 。 （如果是這種情況，您也可以嘗試stripprefix-traefik中間件）

以上只是示例，您可以看到很明顯您有一個循環。

✌️