未找到Kubernetes Inress Nginx控制器 [英] Kubernetes Ingress Nginx Controller is Not Found

查看:11
本文介绍了未找到Kubernetes Inress Nginx控制器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Inress Nginx控制器返回404未找到Reaction应用程序。我将范围缩小到Reaction应用程序,因为如果我尝试点击posts.com/post,它实际上会返回现有帖子的JSON列表,但对于前端应用程序,它会一直显示 获取http://posts.com/404(未找到)

我查看了其他一些堆栈溢出问题,不幸的是无济于事。

inress-srv.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-srv
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/use-regex: "use"
spec:
  rules:
    - host: posts.com
      http:
        paths:
          - path: /posts/create
            pathType: Prefix
            backend:
              service:
                name: posts-clusterip-srv
                port:
                  number: 4000
          - path: /posts
            pathType: Prefix
            backend:
              service:
                name: query-srv
                port:
                  number: 4002
          - path: /posts/?(.*)/comments
            pathType: Prefix
            backend:
              service:
                name: comments-srv
                port:
                  number: 4001
          - path: /?(.*)
            pathType: Prefix
            backend:
              service:
                name: client-srv
                port:
                  number: 3000

客户端耗尽.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: client-depl
spec: 
  replicas: 1
  selector:
    matchLabels:
      app: client
  template:
    metadata:
      labels:
        app: client
    spec:
      containers:
        - name: client
          image: brachikaa/client
          imagePullPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
  name: client-srv
spec:
  selector: 
    app: client
  ports: 
    - name: client
      protocol: TCP
      port: 3000
      targetPort: 3000
          

前端文档文件

FROM node:alpine

ENV CI=true

WORKDIR /app
COPY package.json ./
RUN npm install
COPY ./ ./ 

CMD ["npm", "start"]

记录Pod:

Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  11m   default-scheduler  Successfully assigned default/client-depl-f7cf996cf-cvh6m to minikube
  Normal  Pulling    11m   kubelet            Pulling image "brachikaa/client"
  Normal  Pulled     11m   kubelet            Successfully pulled image "brachikaa/client" in 42.832431635s
  Normal  Created    11m   kubelet            Created container client
  Normal  Started    11m   kubelet            Started container client

如果您需要其他日志,我很乐意提供。谢谢。

推荐答案

所以这个问题非常愚蠢-我实际上设置了nginx.ingress.kubernetes.io/Use-regex:";而不是nginx.ingress.kubernetes.io/Use-regex:&true";...经过三天的文档检查,我终于找到了它。如果任何人遇到类似的问题--这就是问题所在。

这篇关于未找到Kubernetes Inress Nginx控制器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆