Error in EKS Console Upgrade insights about flowschemas and priorityleveconfiguration api's

Hello @Ross. The upgrade happened without any issues. It looks like this is just a message and does not affect the upgrade. If there is a new version available, announced by AWS, you should be able to upgrade without any issues.

It seems AWS will show the warning even if API is not really used - if any client was accessing this API recently - you will see a warning

in my case I was following one of the community guides to upgrade EKS that included the tool called kubent - the one that checks for depreacated APIs - it was accessing the API to check its version and that's why the warning appeared

You can click on the API link and you will see who was the last one accessing the API - most likely you will see similar client

In our case we then ignored this warning and just proceeded with upgrade

Based on the error message you provided, some potential causes for the failure could be:

• Insufficient IP addresses in the subnets associated with the EKS cluster. Check that there are enough available IPs.
• The subnets specified do not exist or are not tagged correctly. Verify the subnets exist and have the proper tags
• The security groups associated with the cluster do not exist. Check that the security groups exist.
• The elastic network interface limit for the AWS account has been reached. You may need to increase the limit.
• Insufficient permissions for the IAM role/user used to update the cluster. Verify the correct permissions are attached.
• The VPC associated with the cluster no longer exists. Check that the VPC still exists.
• Transient backend workflow issues. Try updating the cluster again after some time.

You can get more details on the specific error by describing the update failure with the AWS CLI:

aws eks describe-update --cluster-name my-cluster --update-id my-update-id

I'm experiencing the same issue. I've nothing installed on the cluster which is using flow control. I managed to delete this API service , but seems that something is adding it automatically without interaction from my side. Checked if this API service version persist in my cluster: kubectl get apiservice | grep v1beta3.flowcontrol.apiserver.k8s.io Deleted with kubectl delete apiservice v1beta3.flowcontrol.apiserver.k8s.io Now I am awaiting for AWS to rescan my cluster and to find out if this insight error will disappear.

Good day all, We are currently facing this same issue upgrading EKS from v1.31 to v1.32.

We do not see that we have any manifest or any calls to v3beta flowschemas. All api's are on v1:

kubectl api-resources | grep -i flow NAME SHORTNAMES APIVERSION NAMESPACED KIND flowschemas flowcontrol.apiserver.k8s.io/v1 false FlowSchema prioritylevelconfigurations flowcontrol.apiserver.k8s.io/v1 false PriorityLevelConfiguration

kubectl describe flowschema eks-workload-high | grep api API Version: flowcontrol.apiserver.k8s.io/v1

Please could anyone advise on possible solution.