每个 HTTPS 入口请求的 404 NOT FOUND 响应答案

【问题标题】：404 NOT FOUND response on every HTTPS Ingress request每个 HTTPS 入口请求的 404 NOT FOUND 响应
【发布时间】：2021-01-06 19:22:14
【问题描述】：

我在 GKE 上部署了多个 Spring Boot 应用程序。每个 Spring Boot 都启用且不受限制的执行器端点。我创建了一个 HTTPS 入口，但我只收到 404 Not Found 响应。

服务概览：

入口 YAML：

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.gcp.kubernetes.io/pre-shared-cert: mcrt-0c6bff90-d2fa-4a14-84b5-779c812a4c0b
    ingress.kubernetes.io/backends: '{"k8s-be-30206--3e15e15e4f605a79":"HEALTHY","k8s-be-31081--3e15e15e4f605a79":"HEALTHY","k8s-be-31129--3e15e15e4f605a79":"HEALTHY","k8s-be-31673--3e15e15e4f605a79":"HEALTHY","k8s-be-32006--3e15e15e4f605a79":"HEALTHY"}'
    ingress.kubernetes.io/https-forwarding-rule: k8s-fws-default-skitter-ingress--3e15e15e4f605a79
    ingress.kubernetes.io/https-target-proxy: k8s-tps-default-skitter-ingress--3e15e15e4f605a79
    ingress.kubernetes.io/ssl-cert: mcrt-0c6bff90-d2fa-4a14-84b5-779c812a4c0b
    ingress.kubernetes.io/url-map: k8s-um-default-skitter-ingress--3e15e15e4f605a79
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{"kubernetes.io/ingress.allow-http":"false","kubernetes.io/ingress.global-static-ip-name":"skitter-ip","networking.gke.io/managed-certificates":"skitterapp.com"},"name":"skitter-ingress","namespace":"default"},"spec":{"rules":[{"host":"skitterapp.com","http":{"paths":[{"backend":{"serviceName":"business-owner-service","servicePort":80},"path":"/business-owner-service/*"},{"backend":{"serviceName":"customer-service","servicePort":80},"path":"/customer-service/*"},{"backend":{"serviceName":"staff-service","servicePort":80},"path":"/staff-service/*"},{"backend":{"serviceName":"sms-service","servicePort":80},"path":"/sms-service/*"}]}}]}}
    kubernetes.io/ingress.allow-http: "false"
    kubernetes.io/ingress.global-static-ip-name: skitter-ip
    networking.gke.io/managed-certificates: skitterapp.com
  creationTimestamp: "2020-09-20T12:10:35Z"
  finalizers:
  - networking.gke.io/ingress-finalizer
  generation: 3
  name: skitter-ingress
  namespace: default
  resourceVersion: "11344191"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/skitter-ingress
  uid: 6b92ff0d-01a2-449f-9cd7-afdd1452e73b
spec:
  rules:
  - host: skitterapp.com
    http:
      paths:
      - backend:
          serviceName: business-owner-service
          servicePort: 80
        path: /business-owner-service/*
      - backend:
          serviceName: customer-service
          servicePort: 80
        path: /customer-service/*
      - backend:
          serviceName: staff-service
          servicePort: 80
        path: /staff-service/*
      - backend:
          serviceName: sms-service
          servicePort: 80
        path: /sms-service/*
status:
  loadBalancer:
    ingress:
    - ip: 35.241.60.223

负载均衡器详细信息（突出显示证书处于活动状态并且一切正常）：

测试请求：https://skitterapp.com/business-owner-service/actuator/health； https://skitterapp.com/customer-service/actuator/health

日志不是很有帮助：

我做错了什么？我希望当我发送请求skitterapp.com/customer-service/actuator/health 时，入口识别/customer-service/**，并将GET 请求/actuator/health 传递给客户服务。但我没有看到这种行为，从我在日志中看到的内容来看，客户服务没有收到健康请求

【问题讨论】：

是否有任何休息控制器服务于此路径，例如 /business-owner-service ？检查入口控制器 pod 的日志。上次我检查 GKE 入口不支持 rewrite-target 就像 nginx 入口控制器一样
您询问的是业务所有者服务，因为它是默认服务，并且可能每个请求都会发送到默认规则？ /business-owner-service 下没有请求
除非您重写目标，否则请求将被发送到该应用程序的该路径而不是根路径。 github.com/kubernetes/ingress-gce/issues/109
" 将被发送到该应用程序的路径而不是根路径" 你能给我一个例子吗？
我认为 ArghyaSadhu 的意思是，如果您要发送如下查询：skitterapp.com/customer-service/hello，它将以 /customer-service/hello 到达 pod。重写可能只有hello。需要在您的 pod 中出现什么 URL 才能使其正常工作？

标签： spring-boot kubernetes google-cloud-platform google-kubernetes-engine kubernetes-ingress

【解决方案1】：

你必须在入口添加这个注解，

nginx.ingress.kubernetes.io/rewrite-target:/

也许这样可以解决问题

【讨论】：