使用入口控制器公开Kubernetes部署(前端) [英] Expose a kubernetes deployment (frontend) using ingress controller

问题描述

我正在Kubernetes上部署许多微服务和Angular前端的Docker容器.我已经使用入口控制器公开了服务，该入口控制器使用此入口指定每个服务，并在后端指定路径.

I am deploying a number of docker containers of micro-services and angular frontend on Kubernetes. I have exposed the services using an ingress controller specifying each service using this, and specifying paths in backend.

apiVersion: extensions/v1beta1
kind: Ingress

对于我的前端，我创建了一个类型为loadbalancer的服务.

For my frontend, I have created a service with type loadbalancer.

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/azure-load-balancer-resource-group: my-resource-group
  name: myapp-svc
  namespace: ui
spec:
  loadBalancerIP: SOME_IP_ADDRESS
  type: LoadBalancer
  ports:
  - port: 80
 selector:
   app: myapp

这可以正常工作，但是现在我有两个IP地址，一个用于UI负载平衡器，另一个用于入口控制器(用于API).

This works fine but now I have two IP addresses, one for the UI loadbalancer, and other of the ingress controller (for APIs).

我可以仅使用一个IP地址吗?

Can I do this with just one IP address?

如何在不创建外部负载均衡器的情况下使用入口控制器本身公开用户界面?

How can I expose the UI using ingress controller itself without creating external loadbalancer?

推荐答案

尝试这种方式-

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/service-upstream: "true"
  name: rule-name
  namespace: default
spec:
  rules:
  - host: hostname
    http:
      paths:
      - backend:
          serviceName: frontend-service
          servicePort: port-number
        path: /(.*)
      - backend:
          serviceName: backend-service
          servicePort: port-number
        path: /api/(.*)

---

您可以使用上面定义的策略，直接在/处映射前端，并使用rewrite-target将主机名/api之类的内容映射到后端服务.

---

You can use the above defined strategy where you can directly map front end at / and use rewrite-target to map anything like hostname/api to backend service.

您只能将前端和后端服务保持在clusterIP级别

You can keep frontend and backend services at clusterIP level only

这篇关于使用入口控制器公开Kubernetes部署(前端)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！