AWS NLB Usage Warning still needed ?

[yogeek]

In the doc Configuring Istio Ingress with AWS NLB, a warning mention a bug in K8S that prevented to create multiple clusters in the same AZ when using NLB ingress.

However, the referenced issue kubernetes/kubernetes#69264 seems to be fixed by kubernetes/kubernetes#74910.

I wondered if this warning is still needed because, although it seems to be fixed, I may have the same problem as stated in this dicuss topic

Does anyone here could tell me if the issue is really fixed ? If so, I would make a PR to remove the warning from the corresponding doc.

[TarekAS]

The bug is only fixed in 1.15 right? Therefore, we might still need this warning.

[davi7461]

Can we have an update on this?

[pwjagrullar]

The doc also states that "Usage of AWS nlb on Kubernetes is an Alpha feature and not recommended for production clusters.".

Is this still valid now 2 years later or is it ok to use AWS NLB in production clusters?

[sbogdanovic]

Besides problems with TLS in versions pre 1.15 and the still existing problem with multiple clusters in the same zone, are there any other known issues with NLB?

[kanapuli]

Istio NLB seems to modify Security groups to expose the nodeports to all IPs. This could be a security problem.

[howardjohn]

The blogs are considered a snapshot in time and have a warning "This blog post was written assuming Istio 1.0, so some of this content may now be outdated.".

We do not intend to keep every blog 100% up to date