Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

EKS v1.32 has error in Upgrade insights

0

I've just upgraded my cluster from v1.29 to v1.32 (v1.29 -> v1.30 -> v1.31 -> v1.32). Everything seems to work fine, but in the Upgrade Insights section, I have two errors:

Upgrade insights

Insight: EKS add-on version compatibility

Recommended action: Upgrade your EKS add-on to a newer version compatible with the next Kubernetes version.

have the following add-ons flagged as Error:

arn:aws:eks:<my_region>:<my_aws_account>:addon/<my_eks>/coredns/<uuid>  v1.11.4-eksbuild.2
arn:aws:eks:<my_region>:<my_aws_account>:addon/<my_eks>/kube-proxy/<uuid> v1.32.0-eksbuild.2
arn:aws:eks:<my_region>:<my_aws_account>:addon/<my_eks>/vpc-cni/<uuid> v1.19.3-eksbuild.1

while this one is flagged as Passing

arn:aws:eks:<my_region>:<my_aws_account>:addon/<my_eks>/aws-ebs-csi-driver/<uuid>

However, I’ve already checked and confirmed that I have the latest available versions installed.

Is this expected behavior?

Insight: Deprecated APIs removed in Kubernetes v1.32

Recommended action: Update manifests and API clients to use newer Kubernetes APIs if applicable before upgrading to Kubernetes v1.32.

However, I don’t use these APIs. Could it be an EKS monitoring service that is using the FlowControl API? I also use Lens with this cluster, could it be that?

api details

Topics
ComputeContainers
Tags
Amazon EKS AnywhereSupport APIKubernetes
Language
English
asked 9 months ago1.6K views
2 Answers
1

Hello, 



The EKS cluster insights gets updated periodically. If you've already upgraded the managed add-ons to the latest compatible version, then it will take some time for cluster insights to update. To determine if a fix was successful, compare the time the change deployed to the "last refresh time" of the cluster insight.

Furthermore, the 'flowcontrol.apiserver.k8s.io/v1beta3" API version is depreciated with kubernetes 1.32, you can use the following command to see if there are any resources using the depreciated API version.



[+] kubectl get flowschemas -A -o yaml | grep "apiVersion: flowcontrol.apiserver.k8s.io/v1beta3" -B5 -A5

I understand that you don't use FlowSchemas. But FlowSchemas are default resources that come with Kubernetes API Priority and Fairness (APF) feature. They're automatically created when you create a cluster. You may use review the existing FlowSchemas using "kubectl get flowschemas".

Additionally, Amazon EKS uses a 30-day rolling window when it reads the Kubernetes audit logs. As a result, Amazon EKS continues to report all deprecated API usage within the last 30 days even after you update the API versions. A check's status remains as Error until the last audit log entry for the check passes the 30-day window.

AWS
answered 8 months ago
0

The behavior you're experiencing with the Upgrade Insights for your EKS cluster is not typical and may indicate some inconsistencies or potential issues. Let's address each insight separately:

  1. EKS add-on version compatibility: It's unusual that you're seeing errors for add-ons that you've confirmed are at their latest available versions. This could be due to a lag in the EKS console updating its information, or there might be a mismatch between what's considered the latest compatible version for the next Kubernetes version and what's currently installed. To resolve this:
  • Double-check the EKS documentation for the most up-to-date add-on versions compatible with your current Kubernetes version and the next version.
  • Consider manually updating these add-ons again, even if they appear to be at the latest version.
  • If the issue persists, it may be worth contacting AWS support to investigate if there's a problem with the Upgrade Insights feature itself.
  1. Deprecated APIs removed in Kubernetes v1.32: The warning about FlowControl APIs is interesting, especially since you mention not using these APIs directly. This could indeed be related to EKS internal components or monitoring services. Lens, being a Kubernetes IDE, shouldn't typically cause this kind of API usage warning. To address this:
  • Review any custom resources or third-party tools you might be using in your cluster that could potentially be using these APIs.
  • Check if there are any EKS-specific components or features enabled that might be utilizing these APIs.
  • Consider running a tool like kube-no-trouble (kubent) to scan your cluster for usage of deprecated APIs.

It's worth noting that Upgrade Insights are meant to be proactive warnings to help prepare for future upgrades. Since you've already successfully upgraded to v1.32, these warnings might be more relevant for potential future upgrades or could be residual information that hasn't been cleared after your recent upgrades.

If these warnings persist and you're certain that your cluster is fully up-to-date and not using any deprecated APIs, it may be worthwhile to report this to AWS support. They can investigate if there's an issue with the Upgrade Insights feature or if there are any hidden components in EKS that are triggering these warnings.
Sources
Best Practices for Cluster Upgrades - Amazon EKS
Error in EKS Console Upgrade insights about flowschemas and priorityleveconfiguration api's | AWS re:Post

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content