The reason is because of the rules.yaml for apigee-rule which had apiVersion: config.istio.io/v1alpha2kind: rulemetadata:name: apigee-rulenamespace: istio-systemspec:match: context.reporter.kind == "inbound"&& destination.namespace == "default"action...

The call reached the istio-proxy of the called-service.Thats why even I am confused why 403 is thrown, apigee is at the mixer and for the ingress, not sure why the service to service interaction is getting interrupted .The log from the called-service...

I tried the URL http://called-service within the cluster(no port required), it din't work. It is not accessible with out the port number.This problem occurred after Apigee adapter integration it was working fine without the integration. That's why th...

Rahul M Where you telling about the below service names ?kubectl get svc --namespace=defaultNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE called-service ClusterIP 10.43.250.126 8091/TCP 5d callerservice ClusterIP 10.43.247.132 8090/TCP 5d

I am using a GKE(google kubernetes environment) cluster