One more thing to note about timeouts in Istio is that in addition to overriding them in route rules, as you did in this task, they can also be overridden on a per-request basis if the application adds an x-envoy-upstream-rq-timeout-ms
header on outbound requests. In the header, the timeout is specified in milliseconds instead of seconds.
Doesn't work in istio-enabled GKE, as right after we try to modify ingressgateway
GKE will try to revert that :(
TODO:
- Install custom istio on GKE
MeshPolicy
is a cluster-wide resource
Only destination rules in the client namespace, server namespace and global namespace (default is istio-system) will be considered for a service, in that order.
DestinationRule
could be created in both source for destination namespace