GKE 上的 Gloo 網關代理外部 IP：telnet：無法連接到遠程主機：連接被拒絕

Question

我在同一個 GKE 集群上部署了 nifi 和 gloo API Gateway。 作為 LoadBalancer 公開的外部 IP 運行良好（在 Web 瀏覽器或 telnet 上打開）。 但是，當我使用 telnet 連接GKE cloud shell上的 gloo API Gateway 時，我的連接被拒絕。

取決於相關原因和解決方案，我通過創建防火牆規則允許流量流入集群：

gcloud compute firewall-rules create my-rule --allow=all

我該怎么辦？

kubectl get -n gloo-system service/gateway-proxy-v2 -o yaml

apiVersion: v1
kind: Service
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"gloo","gateway-proxy-id":"gateway-proxy-v2","gloo":"gateway-proxy"},"name":"gateway-proxy-v2","namespace":"gloo-system"},"spec":{"ports":[{"name":"http","port":80,"protocol":"TCP","targetPort":8080},{"name":"https","port":443,"protocol":"TCP","targetPort":8443}],"selector":{"gateway-proxy":"live","gateway-proxy-id":"gateway-proxy-v2"},"type":"LoadBalancer"}}
  labels:
    app: gloo
    gateway-proxy-id: gateway-proxy-v2
    gloo: gateway-proxy
  name: gateway-proxy-v2
  namespace: gloo-system
spec:
  clusterIP: 10.122.10.215
  externalTrafficPolicy: Cluster
  ports:
  - name: http
    nodePort: 30189
    port: 80
    protocol: TCP
    targetPort: 8080
  - name: https
    nodePort: 30741
    port: 443
    protocol: TCP
    targetPort: 8443
  selector:
    gateway-proxy: live
    gateway-proxy-id: gateway-proxy-v2
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: 34.xx.xx.xx

kubectl get svc -n gloo-system

NAME               TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
gateway-proxy-v2   LoadBalancer   10.122.10.215   34.xx.xx.xx   80:30189/TCP,443:30741/TCP   63m
gloo               ClusterIP      10.122.5.253    <none>        9977/TCP                     63m

Answer 1

您可以嘗試使用 Gloo 版本1.3.6 。

請查看https://docs.solo.io/gloo/latest/upgrading/1.0.0/以跟蹤任何可能的重大更改。