Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

API Ingress Troubleshooting

Yuriy Lesyuk edited this page Nov 10, 2020 · 1 revision

API ring-out

Checking a ping proxy along its execution path.

dc1-cluster

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

Getting busyboxplus:curl shell

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

Scenarios



Deep Dives

Archive

Ingress and TLS

DevPortal

Troubleshooting Flows

Clone this wiki locally