Question

我无法使用props下的任何路径来使用GKE Ingress，而且我也不明白为什么。我尝试路线时得到404。

对于下面的示例，我希望- host: api.mysite.com和api.mysite.com/v1/路由到适当的服务（我已通过nodeport公开）。不幸的是，我只有404退还给我。

api.mysite.com/v2/

公开服务的节点端口：

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: gce-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.global-static-ip-name: my-global-ip
spec:
  rules:
  - host: mysite.com
    http:
      paths:
      - backend:
        serviceName: webserver
        servicePort: 8080
  - host: www.mysite.com
    http:
      paths:
      - backend:
        serviceName: webserver
        servicePort: 8080
  - host: api.mysite.com
    http:
      paths:
      - path: /v2/*
        backend:
          serviceName: api-v2
          servicePort: 9000
      - path: /v1/*
        backend:
          serviceName: api-v1
          servicePort: 8000

测试入口时的结果（真实主机名和ip已编辑）：

apiVersion: v1
kind: Service
metadata:
  name: webserver
  labels:
    app: webserver
  namespace: default
spec:
  selector:
    app: webserver
  type: NodePort
  ports:
  - port: 8080
    name: http
    protocol: TCP
    targetPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: api-v2
  labels:
    app: api-v2
  namespace: default
spec:
  selector:
    app: api-v2
  type: NodePort
  ports:
  - port: 9000
    name: http
    protocol: TCP
    targetPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: api-v1
  labels:
    app: api-v1
  namespace: default
spec:
  selector:
    app: api-v1
  type: NodePort
  ports:
  - port: 8000
    name: http
    protocol: TCP
    targetPort: 8080

$ curl api.mysite.com/v1/ -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 123.123.123.123...
* TCP_NODELAY set
* Connected to api.mysite.com (123.123.123.123) port 80 (#0)
> GET /v1/ HTTP/1.1
> Host: api.mysite.com
> User-Agent: curl/7.55.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Server: gunicorn/19.9.0
< Date: Mon, 24 Jun 2019 00:01:34 GMT
< Content-Type: text/html
< X-Frame-Options: SAMEORIGIN
< Content-Length: 77
< Via: 1.1 google
<
{ [77 bytes data]
100    77  100    77    0     0     77      0  0:00:01 --:--:--  0:00:01   706
* Connection #0 to host api.mysite.com left intact
<h1>Not Found</h1><p>The requested resource was not found on this server.</p>

$ curl api.mysite.com/v2/ -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 123.123.123.123...
* TCP_NODELAY set
* Connected to api.mysite.com (123.123.123.123) port 80 (#0)
> GET /v2/ HTTP/1.1
> Host: api.mysite.com
> User-Agent: curl/7.55.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Server: gunicorn/19.9.0
< Date: Mon, 24 Jun 2019 00:01:37 GMT
< Content-Type: text/html
< X-Frame-Options: SAMEORIGIN
< Content-Length: 77
< Via: 1.1 google
<
{ [77 bytes data]
100    77  100    77    0     0     77      0  0:00:01 --:--:--  0:00:01   987
* Connection #0 to host api.mysite.com left intact
<h1>Not Found</h1><p>The requested resource was not found on this server.</p>

$ curl api.mysite.com/v1 -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 123.123.123.123...
* TCP_NODELAY set
* Connected to api.mysite.com (123.123.123.123) port 80 (#0)
> GET /v1 HTTP/1.1
> Host: api.mysite.com
> User-Agent: curl/7.55.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Mon, 24 Jun 2019 00:01:40 GMT
< Content-Length: 21
< Content-Type: text/plain; charset=utf-8
< Via: 1.1 google
<
{ [21 bytes data]
100    21  100    21    0     0     21      0  0:00:01 --:--:--  0:00:01   269
* Connection #0 to host api.mysite.com left intact
default backend - 404

Answer 1

为了重现该问题，我遵循了下一个文档，该文档解释了如何使用Ingress设置HTTP负载平衡，然后作为一项可选操作，您可以保留静态IP地址并在同一负载均衡器上服务多个应用程序。

按照上述网址逐步操作对我来说很好：

https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer

希望它对您有用。

GKE入口无法在一个主机下路由多个路径

1 个答案: