k8s ingress controller相当于ALB,端口都在controller里设置好,ingress相当于监听器,svc是后端,相当于target group?
Cluster IP模式,kubectl expose deployment test-load --type=ClusterIP --port=8080 --target-port=80 --name=hello-svc
可以通过8080和8443两个端口访问(在controller里设置)
NodePort模式,kubectl expose deployment test-load --type=NodePort --port=8081 --target-port=80 --name=node-svc
node的IP+60000以上的端口访问。
更新:
LoadBalancer 模式, 相当于直接部署了ALB,通过deployment
#kubectl get svc -o wide -n kong-sit
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
guec-kong-lb-svc LoadBalancer 10.100.212.177 internal-a886f5940bff245b3a52df35efa6a21b-206400860.ap-northeast-1.elb.amazonaws.com 8000:31197/TCP 43d app=ec-ingress-kong
guepay-kong-lb-svc LoadBalancer 10.100.10.210 internal-a0b231ce1a010481293d40fb1f252968-1539474901.ap-northeast-1.elb.amazonaws.com 8000:31100/TCP 17d app=epay-ingress-kong
gughq-kong-lb-svc LoadBalancer 10.100.213.106 internal-a9bd3a6f4413e4b70854a8a81c64051a-1409233828.ap-northeast-1.elb.amazonaws.com 8000:31198/TCP 18d app=ghq-ingress-kong
详细看这里:
Network load balancing on Amazon EKS - Amazon EKS