Reading the docs on the activator, it seems to create k8s ingress objects and forwarding to another service in the backend that does actual routing. This is an unnecessary hop if I am understanding this correctly. Using an Istio gateway with a LoadBalancer, you can completely get same basic functionality as Ingress, and more. You can define new servers in the gateway for each host and define virtual services for those servers dynamically. Traffic will go from the gateway to the backing service directly instead of bouncing across another intermediary.
Last but not least, use of ingress controller in istio is sort of discouraged (meant only for users migrating from existing stuff). The gateways offer a lot more flexibility.
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Additional Info
Reading the docs on the activator, it seems to create k8s ingress objects and forwarding to another service in the backend that does actual routing. This is an unnecessary hop if I am understanding this correctly. Using an Istio gateway with a LoadBalancer, you can completely get same basic functionality as Ingress, and more. You can define new servers in the gateway for each host and define virtual services for those servers dynamically. Traffic will go from the gateway to the backing service directly instead of bouncing across another intermediary.
Last but not least, use of ingress controller in istio is sort of discouraged (meant only for users migrating from existing stuff). The gateways offer a lot more flexibility.
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Additional Info