0

我在同一个 GKE 集群上部署了 nifi 和 gloo API Gateway。作为 LoadBalancer 公开的外部 IP 运行良好（在 Web 浏览器或 telnet 上打开）。但是，当我使用 telnet 连接 gloo API Gateway on 时GKE cloud shell，我的连接被拒绝。

取决于相关原因和解决方案，我通过创建防火墙规则允许流量流入集群：

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 获取 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
4

1 回答 1

0

您可以尝试使用 Gloo 版本1.3.6。

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

于 2020-02-20T18:13:10.280 回答