Describe the bug
We’ve successfully deployed the Single control plane topology with two clusters.
Now we have istio gateways installed in both clusters. But gateway rules in istio-remote cluster does not take effect.
If I config gateway rules only on remote cluster, no final rule is generated:
[root@iZ2zegdhs7pd18ik2o49fsZ ~]# istioctl pc routes istio-ingressgateway-84b4868f6b-jqkdq -o json
[
{
"virtualHosts": [
{
"name": "backend",
"domains": [
"*"
],
"routes": [
{
"match": {
"prefix": "/stats/prometheus"
},
"route": {
"cluster": "prometheus_stats"
}
}
]
}
]
}
]
Expected behavior
Gateway rules in istio-remote cluster take effect.
Steps to reproduce the bug
Config gateways and related virtualservices in both clusters of a Single control plane topology.
Version
➜ ~ istioctl version
Version: 1.0.5
GitRevision: c1707e45e71c75d74bf3a5dec8c7086f32f32fad
User: root@6f6ea1061f2b
Hub: docker.io/istio
GolangVersion: go1.10.4
BuildStatus: Clean
➜ ~ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T22:29:25Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Installation
Alibaba Cloud -> Istio helm chart
Environment
Alibaba Cloud
Cluster state
No need to provide