1 回答
- 最新
- 投票最多
- 评论最多
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.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 个月前