2 Answers
- Newest
- Most votes
- Most comments
0
Can you please provide more details of your error. Looks like it's application specific, did you check deprecation guide for moving from 1.21 to 1.22 https://kubernetes.io/docs/reference/using-api/deprecation-guide/. Make sure your application is not using any deprecated API versions.
answered 2 years ago
0
Hello,
So the error could be due to many reasons. In order to find a cause behind the error I would suggest you to perform below set of actions and see if that help you in finding the issue.
- kubectl get pods -o wide ---> Look for the application pods which you are trying to connect to
- kubectl get svc ---> look for the service which is front ending the pods
- kubectl describe svc <service-name> ---> Look for the endpoints in the output and compare if they are reffering to right pods by matching the IP.
- kubectl get ing --> Look for the ingress which has the above service as backend.
- kubectl describe ing <ingress-name> ---> Check for the events in the output and see if there is any error.
- In AWS console, go the the load balancer section and look for the target group and check for the registered targets, are they having the same IP as your pods(in case of IP type target) or node IP( in case of instance type target)
- Check if the targets are healthy?
- If you do not see any targets in the target group, look for the controller logs.
I hope above steps will help you in narrowing down the issue. Please let me know if there is any error which you are not able to figure out or above steps does not helps you.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 15 days ago
- AWS OFFICIALUpdated a year ago
Are you using an old version of nginx ingress controller? Because 1.22 removed some deprecated API versions for ingress related resources, which causes the ingress controller to crash. I had similar issue (on test setup first), and moved to more recent version of ingress controller.