大网数据广告活动
服务器运维问答

Need help on loadbalancer connection to nginx ingress controller

· 52CE 我爱测

apiVersion: v1 kind: Service metadata: name: ingress-nginx namespace: ingress-nginx labels: app: ingress-nginx spec: type: LoadBalancer externalIPs: - {{ vip_address }} ports: - port: 80 targetPort: 80 selector: app: ingress-ngin…

问题原文

原帖链接 · rufus · CC BY-SA 4.0

apiVersion: v1
kind: Service
metadata:
  name: ingress-nginx
  namespace: ingress-nginx
  labels:
    app: ingress-nginx
spec:
  type: LoadBalancer
  externalIPs:
  - {{  vip_address }}
  ports:
  - port: 80
    targetPort: 80
  selector:
    app: ingress-nginx

PublicIP/ElasticIP ==> AWS ELB/CLB ==> VIP/PrivateIP(NGINX Ingress Controller) ==> for access to k8s service.

I already have the Ingress controller running on k8s master in ec2 node.
Is there any particular type such as Classic or Application LB need to be chosen since static IP is used?
Also, can I do a standalone provisioning of the LB and configure the traffic to be forwarded to vip?

已采纳解答

原帖链接 · frsechet · CC BY-SA 4.0

You can not use an Elastic IP with an ALB/ELB.

Either you can assign an EIP to one EC2 instance directly or you can use an ALB (or classic ELB) but then you do not get a static IP, just a fixed hostname (that you can use a CNAME with).

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-12-26)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。