-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
│ Error: Failed to create Ingress 'prod/htd-ingress' because: Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws": the server could not find the requested resource #2039
Comments
I've got the same problem, EKS 1.20.
|
I've got the same problem as well Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws": the server could not find the requested resource |
I've solved this issue by reapplying service account on a cluster - might be unrelated but you can give it a try
also replace namespace to |
It's helpful to solve problem! Just overriding existing service account does not work. It's working after deleted iam service account and recreated it. |
Same issue on I updated the CRD manually Has anyone figured out the root cause of this issue? |
@giannisbetas, do you see any errors in the controller logs? |
@kishorj I updated the IAM policy and the CRDs. I could not see any errors in the logs of the controller. |
able to solve the issue by redeploying the serviceaccount thanks for the help. |
@dilip-joveo I'm facing the same proble in eks 1.19, how did you redeploy the serviceaccount? In my case i am using helm and the chart creates the service account
|
Following this official AWS guide helped me https://aws.amazon.com/premiumsupport/knowledge-center/eks-alb-ingress-controller-fargate/ |
I just have the same issue, with 1.21 eks.
error
|
I followed like 5 guides, all from Amazon, but none worked, they either lacked information or were outdated. This one worked! Finally! |
It can be caused by the updated iam_policy.json file. If you are using local/downloaded policies make sure they are up to date with the latest version of aws-load-balancer-controller. |
In case it might help others - I also had the original issue using fargate profile and worker-node for core-dns. The solution for me I found in another place was just adding
|
Thanks @eocern . Saved my day. :) A hint for people from the future struggeling to find why they get |
For me, I had to open TCP 9443 port from the control plane to the nodes |
Thanks @eocern this is the solution for me |
Thanks @eocern, this solution works for me too =) |
The same problem is possible when using recent AWS Load Balancer Controller Docker images (2.4.x) with an outdated Helm chart. My setup:
In this setup, I get the same problem which is discussed in this thread: Solution - update CDK to more recent version which deploys AWS Load Balancer Controller using more recent Helm chart. |
Where I need to add this ? |
Take a look here: #2039 (comment) |
Have deployed aws-load-balancer controller using the helm chart in eks cluster while creating the ingress of the of the service getting the error
│ Error: Failed to create Ingress 'prod/htd-ingress' because: Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws": the server could not find the requested resource
The text was updated successfully, but these errors were encountered: