[ICN-381] Test forwarding traffic to custom suffix

Relates — Thu, 22 Oct 2020 00:02:10 +0000

According to Itohan:

"By default, when istio is installed, it only allows forwarding traffic to services in the remote cluster with the "global" suffix. In order to enable istio to forward traffic, we need to change the suffix in some of its resources. Get the following istio resources and edit them (kubectl edit <resource-type> <resource-name> -n <resource-namespace>), change all occurences of the global suffix in each of these resources to your custom suffix.

Add lc1 stubdomain in kube-system coredns cm
Change istio coredns cm to new suffix
Edit envoyfilter to use customsuffix
Edit istio ingressgateway to use custom suffix
Edit istio destination rule to use custom suffix
Make sure service entry uses the right suffix

Note: I have only tested using one custom suffix (e.g) lc1 at a time, I have not tested adding multiple custom suffixes."

I will test this and provide results/conclusions here.

Akraino JIRA

[ICN-381] Test forwarding traffic to custom suffix