1 Answer
- Newest
- Most votes
- Most comments
0
hello, this can happen when all the steps for creating the managed endpoint were not followed properly. You can follow below docs :
https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/connect-emr-studio.html https://catalog.us-east-1.prod.workshops.aws/workshops/1f91e1d4-5587-40ff-8d5d-54fc86e0ddc1/en-US/advanced/emr-studio
In my experience, this usually happens when the loadbalancer and ingress controller has some issue while creation. You should consider checking them, as below :
$ kubectl get deployment -n kube-system aws-load-balancer-controller
NAME READY UP-TO-DATE AVAILABLE AGE
aws-load-balancer-controller 1/1 1 1 2m33s
# you might see some output above, note, it should be ready and available then check the status of ingress controller
$ kubectl get ingress -A
answered 9 months ago
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
Simon did you ever figure this out? Hitting same issue....
Curious if you figured out what the issue was.
Hi, hitting same issue. did you manage to get any hint about the issue?
In my case it was that this doesn't support EKS v1.22. Supports suggestion was to rebuild the cluster as v1.21