Kubernetes GKE:telnet上的Gloo网关代理外部IP:无法连接到远程主机:连接被拒绝

Kubernetes GKE:telnet上的Gloo网关代理外部IP:无法连接到远程主机:连接被拒绝,kubernetes,google-kubernetes-engine,google-cloud-load-balancer,Kubernetes,Google Kubernetes Engine,Google Cloud Load Balancer,我在同一个GKE集群上部署nifi和GLOOAPI网关。作为LoadBalancer公开的外部IP工作正常(在Web浏览器或telnet上打开)。然而,当我使用telnet连接GKE cloud shell上的gloo API网关时,我的连接被拒绝 根据关系原因和解决方案,我已通过创建防火墙规则允许流量流入集群: gcloud compute firewall-rules create my-rule --allow=all 我该怎么办 kubectl get-n gloo系统服务/gatew

我在同一个GKE集群上部署nifi和GLOOAPI网关。作为LoadBalancer公开的外部IP工作正常(在Web浏览器或telnet上打开)。然而,当我使用telnet连接GKE cloud shell上的gloo API网关时,我的连接被拒绝

根据关系原因和解决方案,我已通过创建防火墙规则允许流量流入集群:

gcloud compute firewall-rules create my-rule --allow=all
我该怎么办

kubectl get-n gloo系统服务/gateway-proxy-v2-o yaml

kubectl get svc-n gloo系统

名称类型群集IP外部IP端口
gateway-proxy-v2负载平衡器10.122.10.215 34.xx.xx.xx 80:30189/TCP,443:30741/TCP 63m
gloo ClusterIP 10.122.5.253 9977/TCP 63m

您可以尝试跳到Gloo版本
1.3.6


请查看以跟踪任何可能的中断更改。

您好,是否可以提供连接被拒绝时收到的错误消息+错误代码?这将帮助我更好地理解这个问题。提前感谢!你好@AnthonyLeo:谢谢你的关心。我已经通过重新安装Gloo网关的较低版本(2.0.0)解决了这个问题。很好
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

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