- 最新
- 最多得票
- 最多評論
Deploying an NLB and having a listener are (pretty much) the same thing. If your application is deployed in two AZs then your NLB should as well. Whether you choose to enable cross-zone load balancing or not is up to you - there is extra cost if you do for traffic that goes to NLB in one AZ and then is sent to the other AZ to be processed by your EKS cluster.
There's no issue with having the NLB listener in a public subnet and EKS in a private subnet - in fact, that's strongly recommended.
Note that NLB modifies the DNS records depending on health checks. Each NLB node IP address will appear in DNS if it has at least one healthy target it can send traffic to. If it hasn't got any healthy targets it is removed from DNS - noting that there is always a lag with DNS propagation. If you have a situation where targets are becoming unhealthy on a regular basis this might be the cause of your issue.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 10 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前