API Ingress Troubleshooting
Checking a ping proxy along its execution path.
Identify Cluster IP for apigee-runtime pod in dc1-cluster.
kubectl get svc
Output
apigee-runtime-emea-cs-hybrid-demo2-test ClusterIP 10.48.0.253
Check endpoints for the apigee-runtime-*-test server
k describe svc apigee-runtime-emea-cs-hybrid-demo2-test
Output
...
Endpoints: 10.44.0.11:8443,10.44.1.13:8443
To execute requests within a cluster, we will use busyboxplus:curl container.
# https://hub.docker.com/r/radial/busyboxplus
kubectl --context dc1-cluster run curl --generator=run-pod/v1 -it --image=radial/busyboxplus:curl
After logging into the busybox with curl configured in it:
# dc1-cluster cluster ip
curl https://10.48.0.253:8443/ping -v -k
# dc2-cluster cluster ip
curl https://10.48.16.241:8443/ping -v -k
AHR-*-CTL 
