Spring boot Istio-GKE-gRPC配置流关闭;上游连接错误或在收割台之前断开/重置。重置原因:连接失败

Spring boot Istio-GKE-gRPC配置流关闭;上游连接错误或在收割台之前断开/重置。重置原因:连接失败,spring-boot,google-kubernetes-engine,istio,Spring Boot,Google Kubernetes Engine,Istio,我正在尝试在GKE集群中使用istio 1.1.5最新版本的spring boot micro服务。它抛出错误,吊舱永远不会旋转。如果我在Kubernetes引擎中作为一个单独的服务运行它,它可以完美地工作,但如果使用isito,它就不工作了。使用istio的目的是承载多个微服务,并使用istio提供的功能。这是我的yaml文件: apiVersion: apps/v1beta1 kind: Deployment metadata: name: revenue spec: repli

我正在尝试在GKE集群中使用istio 1.1.5最新版本的spring boot micro服务。它抛出错误,吊舱永远不会旋转。如果我在Kubernetes引擎中作为一个单独的服务运行它,它可以完美地工作,但如果使用isito,它就不工作了。使用istio的目的是承载多个微服务,并使用istio提供的功能。这是我的yaml文件:

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  name: revenue  
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: revenue-serv
        tier: backend
        track: stable
    spec:
      containers:
        - name: backend
          image: "gcr.io/finacials/revenue-serv:latest"
          imagePullPolicy: Always
          ports:
          - containerPort: 8081
          livenessProbe:
              httpGet:
                path: /
                port: 8081
              initialDelaySeconds: 15
              timeoutSeconds: 30 
          readinessProbe:
              httpGet:
                path: /
                port: 8081
              initialDelaySeconds: 15
              timeoutSeconds: 30
---
apiVersion: v1
kind: Service
metadata:
  name: revenue-serv
spec:
  ports:
    - port: 8081
      #targetPort: 8081
      #protocol: TCP
      name: http 
  selector:
    app: revenue-serv
    tier: backend
  type: LoadBalancer
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: gateway
  annotations:
    kubernetes.io/ingress.class: "istio"
spec:
  rules:
  - http:
      paths:
      - path: /revenue/.*
        backend:
          serviceName: revenue-serv
          servicePort: 8081

感谢您的宝贵反馈。

我发现了这个问题。我删除了ReadynesProbe和livenessProbe,创建了ingressgateway和虚拟服务。成功了

部署和服务:

#########################################################################################
# This is for deployment - Service & Deployment in Kubernetes            ################
# Author: Arindam Banerjee                                               ################
#########################################################################################

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  name: revenue-serv
  namespace: dev  
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: revenue-serv
        version: v1
    spec:
      containers:
        - name: revenue-serv
          image: "eu.gcr.io/rcup-mza-dev/revenue-serv:latest"
          imagePullPolicy: Always
          ports:
          - containerPort: 8081
---
apiVersion: v1
kind: Service
metadata:
  name: revenue-serv
  namespace: dev    
spec:
  ports:
    - port: 8081      
      name: http 
  selector:
    app: revenue-serv
gateway.yaml

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: worldcup-serv-gateway
  namespace: dev
spec:
  selector:
    istio: ingressgateway # use istio default controller
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
虚拟服务.yaml

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: revenue-serv-virtualservice
  namespace: dev  
spec:
  hosts:
  - "*"
  gateways:
  - revenue-serv-gateway
  http:
  - route:
    - destination:
        host: revenue-serv

你能解释一下你是如何得出这个结论的吗?