gke入口无法将流量路由到服务

Question

我正在测试gke入口以将流量路由到两个不同的服务。我的部署包括一个基本的Web容器，它部署了一个默认的蓝色网页和一个绿色网页。我能够得到响应本质上，“/”适用于蓝色或绿色部署。但是当我转到超文本传输协议：///绿色时，我得到了404响应。我已经用“/”作为绿色部署进行了测试，它显示了一个绿色网页。但是如果我转到超文本传输协议：///蓝色，它会导致404响应，

我已经通过将负载平衡器直接连接到容器上来验证容器是否正常工作。我正在学习如何在gke中指导设置类似的环境。GKE入门指南

关于我所缺少的任何帮助都将极大地帮助我更好地了解正在发生的事情以及为什么我的gke负载平衡器无法路由流量。

绿色部署文件

apiVersion: apps/v1
kind: Deployment
metadata: 
  name: myapp-green
spec:
  replicas: 2
  selector:
    matchLabels:
      app: myapp
      version: green
  template:
    metadata:
      name: myapp
      labels:
        app: myapp
        version: green
    spec:
      containers:
        - name: myapp
          image: gcr.io/ultra-welder-300122/myapp:green
          imagePullPolicy: Always
          resources:
            requests:
              cpu: "100m"
              memory: "100Mi"
          ports:
          - containerPort: 8080

蓝色部署文件

apiVersion: apps/v1
kind: Deployment
metadata: 
  name: myapp-blue
spec:
  replicas: 2
  selector:
    matchLabels:
      app: myapp
      version: blue
  template:
    metadata:
      name: myapp
      labels:
        app: myapp
        version: blue
    spec:
      containers:
        - name: myapp
          image: gcr.io/ultra-welder-300122/myapp:blue
          imagePullPolicy: Always
          resources:
            requests:
              cpu: "100m"
              memory: "100Mi"
          ports:
          - containerPort: 8888

我的服务yaml

apiVersion: v1
kind: Service
metadata: 
  name: myapp-blue-service
  labels:
    app: myapp
    version: blue
spec:
  type: NodePort
  selector:
    app: myapp
    version: blue
  ports: 
  - protocol: TCP
    port: 80
    targetPort: 8888
---
apiVersion: v1
kind: Service
metadata: 
  name: myapp-green-service
  labels:
    app: myapp
    version: green
spec:
  type: NodePort
  selector:
    app: myapp
    version: green
  ports: 
  - protocol: TCP
    port: 80
    targetPort: 8080

Gke安格尔亚马尔

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: myapp-ingress
  annotations:
    # If the class annotation is not specified it defaults to "gce".
    kubernetes.io/ingress.class: "gce"
spec:
  rules:
  - http:
      paths:
      - path: /*
        backend:
          serviceName: myapp-blue-service
          servicePort: 80
      - path: /green
        backend:
          serviceName: myapp-green-service
          servicePort: 80

服务状态

NAME                  TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
kubernetes            ClusterIP   10.42.0.1      <none>        443/TCP        6h18m
myapp-blue-service    NodePort    10.42.81.106   <none>        80:31664/TCP   4h35m
myapp-green-service   NodePort    10.42.74.168   <none>        80:30246/TCP   4h35m

入口状态

kubectl describe ing myapp-ingress
Name:             myapp-ingress
Namespace:        default
Address:          34.95.121.24
Default backend:  default-http-backend:80 (10.41.0.9:8080)
Rules:
  Host        Path  Backends
  ----        ----  --------
  *
              /*        myapp-blue-service:80 (10.41.0.24:8888,10.41.1.16:8888)
              /green    myapp-green-service:80 (10.41.0.27:8080,10.41.1.19:8080)
Annotations:  ingress.kubernetes.io/backends:
                {"k8s-be-30192--a4913825f2ae16d4":"HEALTHY","k8s-be-30246--a4913825f2ae16d4":"HEALTHY","k8s-be-31664--a4913825f2ae16d4":"HEALTHY"}
              ingress.kubernetes.io/forwarding-rule: k8s2-fr-dkti1gqp-default-myapp-ingress-yd16xk65
              ingress.kubernetes.io/target-proxy: k8s2-tp-dkti1gqp-default-myapp-ingress-yd16xk65
              ingress.kubernetes.io/url-map: k8s2-um-dkti1gqp-default-myapp-ingress-yd16xk65
              kubernetes.io/ingress.class: gce

部署和pod状态

NAME                                          READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/myapp-blue                    2/2     2            2           4h18m
deployment.apps/myapp-green                   2/2     2            2           38m
NAME                                               READY   STATUS    RESTARTS   AGE
pod/myapp-blue-9c9cbf5b-c7v7c                      1/1     Running   0          4h18m
pod/myapp-blue-9c9cbf5b-cpvgl                      1/1     Running   0          4h18m
pod/myapp-green-7f56cc9496-hnfkz                   1/1     Running   0          38m
pod/myapp-green-7f56cc9496-v8bb6                   1/1     Running   0          38m

服务状态

NAME                  TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
kubernetes            ClusterIP   10.42.0.1      <none>        443/TCP        6h24m
myapp-blue-service    NodePort    10.42.81.106   <none>        80:31664/TCP   4h40m
myapp-green-service   NodePort    10.42.74.168   <none>        80:30246/TCP   4h40m

Answer 1

我发现问题出在gke入口控制器上。Gke ingress controller不向/提供重写目标。我正在从webroot提供我的绿色和蓝色网页。GKE入口控制器正在转发请求的URLhttp://34.95.121.24/green到http://{backend}/green。在http://{backend}/green上没有托管的页面，因为我的默认页面托管在http://{backend}/。

这个问题有两种解决方案。

1. 使用带有注释的nginx入口控制器将目标集重写为/

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - http:
      paths:
      - path: /*
        backend:
          serviceName: myapp-blue-service
          servicePort: 80
      - path: /green
        backend:
          serviceName: myapp-green-service
          servicePort: 80

我创建了一个默认的服务器配置部分，以将任何命中/绿色的流量路由到索引。html。

server {
        listen 80 default_server;
        listen [::]:80 default_server;

        root /var/www/html;
        server_name _;
        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                index index.html
                try_files $uri $uri/ =404;
        }
        location /green {
                try_files $uri $uri/ /index.html;
        }

我将默认站点配置复制到docker配置文件中可用的/etc/nginx/sites。

我的示例Dockerfile

FROM ubuntu
RUN apt-get update
RUN apt-get install nginx -y
COPY index.html /var/www/html/
COPY default /etc/nginx/sites-available/
EXPOSE 80
CMD ["nginx","-g","daemon off;"]