Closed zibuyule closed 1 year ago
Hi can you check if the target groups are up and healthy? You can go to AWS console, EC2 -> Target Groups and click on the corresponding TG.
@zibuyule, you could enable access logs on your ALB, and get the logs from S3. For details, please refer to setting the load balancer attributes: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#load-balancer-attributes
I have a feeling that you are using ALB and ingress resources . but the service is ClusterIP and you are not using aws VPC CNI
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@zibuyule, I'm closing the issue as for now, please feel free to reach out or reopen if you have more questions. Thanks
When I created an ingress resource as follows, I got 502 when I accessed it in the browser. And I access it from another pod within kubernetes and it seems to be working normally.
How can I check for this error?
First, I tried checking the logs of pod: aws-load-balancer-controller-79f55f66d6-rvkwn. It looks like it only prints the logs for creating the AWS ALB.
So where do I go to check the access logs?
Thanks!