-
Notifications
You must be signed in to change notification settings - Fork 743
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
The user eks:vpc-resource-controller doesn't have permission to patch cninode #2926
Comments
@weijiany thanks for the report. The fix from EKS on 1.29 clusters is in progress for this issue. You can apply this manifest file in your cluster to add the missing permissions and required fields in the CRD on 1.29:
|
Hi @sushrk thanks for your reply, I saw that the latest EKS version is 1.30, does it be fixed in this version? |
I upgrade EKS to 1.30, this alert doesn't appear anymore. It looks like it has been resolved in 1.30, I will close this issue. Thanks @sushrk help. 😃 |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Thank you. This issue has been resolved across all available EKS versions. |
What happened:
I used the latest vpc-cni(v1.18.1-eksbuild.3) and enabled the pod eni(ENABLE_POD_ENI) in environment variables, then I alwasy received an alerat:
{@usr.id:eks:vpc-resource-controller} A Kubernetes user attempted to perform a high number of actions that were denied
. I found that there are a lot of error messages in CloudWatchcninodes.vpcresources.k8s.aws \"ip-[ip].[region].compute.internal\" is forbidden: User \"eks:vpc-resource-controller\" cannot patch resource \"cninodes\" in API group \"vpcresources.k8s.aws\" at the cluster scope
.I don't know what happened in EKS cluster, and it caused a lot of noise alerts.
Attach logs
What you expected to happen:
Don't raise this error.
How to reproduce it (as minimally and precisely as possible):
1. Run the following terraform configurations.
"eks:vpc-resource-controller" patch cninode
, you will find the 403 Failure.Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: