NginxKubernetes入口回傳502-有解無憂

我正在嘗試在 AWS EKS 的 Kubernetes 集群中部署簡單的 REST API 應用程式。其他一切都是反向代理就好了。

我使用以下配置進行部署。Pod 是健康的，Pod 每 20 分鐘重新啟動一次，因為 AWS 終止了與我的開發免費層資料庫的連接，但我運行了幾個副本以防萬一。

當我嘗試連接到域時，我收到 502 Bad Gateway 錯誤。我真的不知道發生了什么事。

apiVersion: apps/v1
kind: Deployment
metadata:
  name: xyz-microservice
spec:
  replicas: 4
  template:
    nodeSelector:
        node.kubernetes.io/role: worker
    tolerations:
      - effect: NoSchedule
        key: node.kubernetes.io/role
        operator: Equal
        value: worker
  selector:
    matchLabels:
      app: xyz-microservice
  template:
    metadata:
      labels:
        app: xyz-microservice
    spec:
      hostname: xyz-microservice
      containers:
      - name: xyz-microservice
        image:  redacted
        imagePullPolicy: Always
        env:
        - name: DB_USERNAME
          value: redacted
        - name: DB_PASSWORD
          value: redacted
        - name: DB_HOST
          value: redacted
        - name: DB_PORT
          value: "5432"
        - name: DB_NAME
          value: redacted
        resources:
          requests:
            memory: "32Mi"
            cpu: "80m"
          limits:
            memory: "128Mi"
            cpu: "100m"
        ports:
        - containerPort: 8080

---
apiVersion: v1
kind: Service
metadata:
  name: xyz-microservice-service
spec:
  type: ClusterIP
  selector:
    app: xyz-microservice
  ports:
  - port: 80
    targetPort: 8080
    protocol: TCP

這是入口配置：

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "internal"
    forecastle.stakater.com/expose: "true"
    forecastle.stakater.com/appName: "XYZ Microservice"
    cert-manager.io/cluster-issuer: "letsencrypt-aws"
  name: xyz-microservice
spec:
  rules:
    - host: xyz.internal.staging.k8s.redacted
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: xyz-microservice-service
                port:
                  number: 8080
  tls:
    - hosts:
      - xyz.internal.staging.k8s.redacted
      secretName: xyz-microservice-tls

如果有人可以指導我完成這將意味著很多。

uj5u.com熱心網友回復：

請記住，幾乎每次您在 nginx-ingress 中遇到 502 錯誤網關時，它都與后端埠系結問題/錯誤的后端配置名稱等相關聯。

在這里，您的 nginx 入口配置為將流量從“xyz.internal.staging.k8s.redacted”主機重定向到“xyz-microservice-service”kubernetes 服務的埠 8080。

但是 8080 是您服務的目標埠。沒有暴露的埠，實際上是 80。

因此，要解決此問題，只需更改后端服務的埠，如下所示：

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "internal"
    forecastle.stakater.com/expose: "true"
    forecastle.stakater.com/appName: "XYZ Microservice"
    cert-manager.io/cluster-issuer: "letsencrypt-aws"
  name: xyz-microservice
spec:
  rules:
    - host: xyz.internal.staging.k8s.redacted
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: xyz-microservice-service
                port:
                  number: 80
  tls:
    - hosts:
      - xyz.internal.staging.k8s.redacted
      secretName: xyz-microservice-tls

（或者重新配置服務的埠以匹配入口配置的埠。）

轉載請註明出處，本文鏈接：https://www.uj5u.com/qukuanlian/470196.html

標籤：nginx Kubernetes nginx入口

上一篇：Kubernetespod宕機

下一篇：NginxIngress控制器性能問題