istio.io/content/docs/tasks/traffic-management
Vadim Eisenberg 2f1e1a6020 Use two separate ingress gateways for two hosts (#3529)
* use a separate gateway for bookinfo in the case of multiple hosts

* set the name parameter to be "istio" instead of "istio-ingressgateway"

Since the original istio-ingressgateway was deployed with the name parameter "istio".
Otherwise, the following error will be received:

The Deployment "istio-ingressgateway" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"chart":"gateways", "heritage":"Tiller", "istio":"ingressgateway", "release":"istio-ingressgateway", "app":"istio-ingressgateway"}: `selector` does not match template `labels`

The problem is that the "release" label contains the name parameter of helm template,
and if this label will not match in the new and the original deployments of istio-ingressgateway,
kubectl apply will fail.
2019-03-06 09:07:30 -08:00
..
circuit-breaking add start-httpbin-service boilerplate (#3514) 2019-03-05 10:03:32 -08:00
egress Clean up keywords. (#3442) 2019-02-28 17:26:46 -08:00
fault-injection Reminders to apply destination rules (#3390) 2019-02-26 12:06:19 -08:00
ingress add ingress troubleshooting section (#3410) 2019-03-06 08:59:38 -08:00
mirroring Add a step to look inside mirroring traffic with tcpdump in istio-proxy (#3267) 2019-02-26 14:27:32 -08:00
request-routing Clean up keywords. (#3442) 2019-02-28 17:26:46 -08:00
request-timeouts Reminders to apply destination rules (#3390) 2019-02-26 12:06:19 -08:00
secure-ingress Use two separate ingress gateways for two hosts (#3529) 2019-03-06 09:07:30 -08:00
tcp-traffic-shifting Organize the Kubernetes Installation content. (#3422) 2019-02-28 14:37:30 -08:00
traffic-shifting Reminders to apply destination rules (#3390) 2019-02-26 12:06:19 -08:00
_index.md Clean up a bunch of loose ends (#2745) 2018-10-05 22:21:56 -07:00