1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
A few things you can check to troubleshoot accessing the Kong admin API:
- Verify the security group and network access configuration on the Kong load balancer matches what is used in the existing setup. This includes ingress rules on the load balancer SG and route tables/network ACLs.
- Check that the Kong pods are running successfully with
kubectl get pods -n kong
and the load balancer controller logs for any errors withkubectl logs -n kube-system deployment.apps/aws-load-balancer-controller
- Confirm the Kong Ingress resource is created correctly with
kubectl get ingress -n kong
- Validate the load balancer is provisioned by checking for it in the AWS EC2 console. Its DNS name should resolve to the Kong admin API URL.
- Test connectivity from your machine to the load balancer endpoint/URL using curl. If it fails, check firewall rules or proxy/VPN settings.
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a 4 mois
- demandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an