Adapter for Envoy not working with Istio enabled GKE
I have a GKE with Istio installed, I tried to use APIGEE Public Edge so for that I'm using Adapter for envoy. I followed the all the steps from the APIGEE document but I constantly get 403 Forbidden response.
After that, I followed the exact same steps from the document used the same httpbin example but still getting response- 403 forbidden.
Before it, I used Adapter for Istio and it's working but now it is depreciated.
Kindly assit me if anyone use this in Kubernetes.
Answer by deboraelkin
·
Aug 25, 2020 at 12:04 AM
A few things to look at:
- Have you checked that the remote-service proxy in your Apigee org/env is getting any traffic? If not, it means that your apigee-remote-service deployment is not able to communicate. Check its logs
- Have you defined a product to include your httpbin Istio service (httpbin.default.svc.cluster.local/headers) . Make sure you invoke that endpoint in your tests
- If you delete the envoyfilter-sidecar.yaml configuration (kubectl delete -f ...), are you able to invoke your httpbin istio service?
