Kubernetes入口无法获取服务的群集ip

Kubernetes入口无法获取服务的群集ip,kubernetes,cluster-computing,haproxy,calico,Kubernetes,Cluster Computing,Haproxy,Calico,我用印花布和haproxy设置了kubernetes单节点主平面。现在,每当我要创建入口时,地址都保持为空,服务器返回503错误 下面显示了我的kubernetes部署 apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment spec: selector: matchLabels: app: nginx replicas: 1 template: metadata:

我用印花布和haproxy设置了kubernetes单节点主平面。现在,每当我要创建入口时,地址都保持为空,服务器返回503错误

下面显示了我的kubernetes部署

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 1
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - name: nginx
          image: wordpress
          ports:
            - containerPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  ports:
    - port: 8080
      targetPort: 8080
      protocol: TCP
  selector:
    app: nginx
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: web-ingress
spec:
  rules:
    - host: wordpress.example.org
      http:
        paths:
          - path: /
            backend:
              serviceName: nginx-service
              servicePort: 8080
这是我从kubernetes cl的输出

NAME                             HOSTS                   ADDRESS   PORTS   AGE
ingress.extensions/web-ingress   wordpress.example.org             80      35s

NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/kubernetes      ClusterIP   10.96.0.1       <none>        443/TCP    10h
service/nginx-service   ClusterIP   10.97.189.233   <none>        8080/TCP   35s

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.extensions/nginx-deployment   1/1     1            1           35s

NAME                                    READY   STATUS    RESTARTS   AGE
pod/nginx-deployment-7798df5dd5-gnwf2   1/1     Running   0          35s

NAME                      ENDPOINTS              AGE
endpoints/kubernetes      164.68.103.199:6443    10h
endpoints/nginx-service   192.168.104.150:8080   36s
Pascals-MBP-c8a4:api-gateway pascal$
NAME主机地址端口年龄
ingress.extensions/web-ingress wordpress.example.org 80 35s
名称类型CLUSTER-IP外部IP端口年龄
服务/kubernetes ClusterIP 10.96.0.1 443/TCP 10h
服务/nginx服务群集IP 10.97.189.233 8080/TCP 35s
姓名就绪最新可用年龄
deployment.extensions/nginx-deployment 1/1 35s
名称就绪状态重新启动
pod/nginx-deployment-7798df5dd5-gnwf2 1/1运行0 35s
姓名端点年龄
终点/kubernetes 164.68.103.199:6443 10h
端点/nginx服务192.168.104.150:8080 36s
Pascals-MBP-c8a4:api网关pascal$
我期望入口将接收服务的集群ip,并且正在侦听给定的主机uri,并提供除给定503错误之外的其他信息


//编辑:它是一个独立的节点,而不是桌面版本或minikube安装

服务默认类型为ClusterIP,但它仅用于集群内部通信。 对于外部流量,应切换到节点端口类型。 例如:

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  type: NodePort
  ports:
    - port: 80
      targetPort: 8080
      protocol: TCP
      name: http
  selector:
    run: nginx
如果我没有弄错的话,nginx alb控制器允许使用ClusterIP(或LoadBalancer)


更多信息:

此图像的容器端口是80,我暴露了8080。

不工作。入口也无法获取此服务的地址。。。