将nginx入口主机名称引用给内部服务

问题描述 投票:0回答:1

创建所有必需资源并配置nginx-ingress控制器之后。

apiVersion: apps/v1
kind: Deployment
metadata:
  name: user-api
spec:
  replicas: 1
  selector:
    matchLabels:
      app: user-api
  strategy: {}
  template:
    metadata:
      labels:
        app: user-api
    spec:
      dnsPolicy: ClusterFirstWithHostNet
      hostNetwork: true
      containers:
      - name: user-api
        image: doumeyi/user-api-amd64:1.0
        ports:
        - name: user-api
          containerPort: 3000
        resources: {}
---
apiVersion: v1
kind: Service
metadata:
  name: user-api
spec:
  selector:
    app: user-api
  ports:
  - name: user-api
    port: 3000
    targetPort: 3000
  type: LoadBalancer
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: app-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
    - host: example.com
      http:
        paths:
        - path: /user-api
          backend:
            serviceName: user-api
            servicePort: 3000

我可以查看example.com显示404未找到页面,但也无法看到example.com/user-api来显示我在user-api服务中构建的任何消息。

似乎nginx-ingress无法将主机名解析为内部服务,我该如何解决?

kubernetes-ingress nginx-ingress
1个回答
0
投票

[如果NGINX无法找到到您Pod的路线,则不应以404进行响应。相反,它应提供502(错误网关)AFAIK。我认为404来自您的应用程序。

NGINX-Ingress在[0.22]中更改了行为,如here所述入口资源应如下所示:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: app-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
  rules:
    - host: example.com
      http:
        paths:
        - path: /user-api(/|$)(.*)
          backend:
            serviceName: user-api
© www.soinside.com 2019 - 2024. All rights reserved.