[英]Expose a kubernetes deployment (frontend) using ingress controller
I am deploying a number of docker containers of micro-services and angular frontend on Kubernetes.我在 Kubernetes 上部署了许多 docker 微服务容器和 angular 前端。 I have exposed the services using an ingress controller specifying each service using this, and specifying paths in backend.我已经使用入口 controller 公开了服务,并使用它指定每个服务,并在后端指定路径。
apiVersion: extensions/v1beta1
kind: Ingress
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
This works fine but now I have two IP addresses, one for the UI loadbalancer, and other of the ingress controller (for APIs).这工作正常,但现在我有两个 IP 地址,一个用于 UI 负载均衡器,另一个用于入口 controller(用于 API)。
Can I do this with just one IP address?我可以只使用一个 IP 地址吗?
How can I expose the UI using ingress controller itself without creating external loadbalancer?如何在不创建外部负载均衡器的情况下使用入口 controller 本身公开 UI?
Try this way -试试这个方法——
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/(.*)
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.您可以使用上面定义的策略,您可以直接在 / 的 map 前端使用 rewrite-target 到 map 任何类似主机名/api的后端服务。
You can keep frontend and backend services at clusterIP level only您只能将前端和后端服务保持在 clusterIP 级别
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.