- Newest
- Most votes
- Most comments
hello,
The error you're facing is due to a compatibility issue between the EKS version (v1.30) and the Karpenter version (v1.0.6) you're using. The API versions for Karpenter's custom resources like NodeClaim have changed in v1.0.6, and EKS v1.30 (based on Kubernetes v1.24) may not be compatible with the new API versions yet.
To resolve this:
- Upgrade to a newer compatible version of Karpenter (if available).
- Revert to an older compatible version of Karpenter (e.g., using karpenter.sh/v1beta1 API version).
- Wait for AWS to release a newer EKS version that supports the Kubernetes version compatible with the Karpenter version you want to use.
Ensuring compatibility between Karpenter and EKS/Kubernetes versions is crucial to avoid such issues during upgrades.
Thank you for your question about upgrading EKS Karpenter. The issue you're experiencing is likely related to the compatibility between your Karpenter version and the EKS version you're trying to upgrade to.
Based on the information provided, it seems you've made some of the necessary changes for upgrading to Karpenter v1, which is a good start. However, the error message suggests that there might be additional steps required for a successful upgrade.
Here are a few points to consider:
-
Ensure that you've applied the updated v1 CRDs (Custom Resource Definitions) for NodePool, NodeClaim, and EC2NodeClass before upgrading the Karpenter controller.
-
Upgrade the Karpenter controller to version v1.0.0 or later. This version starts using the v1 API schema in its requests.
-
After upgrading the controller, but before upgrading to Karpenter v1.1.0, you need to update all your v1beta1 manifests to use the new v1 version. This includes considering all API changes for the release.
-
The error message specifically mentions "nodeclaim", which suggests that you might need to update references to this resource in your manifests or ensure that the NodeClaim CRD is properly applied.
-
Double-check that all your Karpenter-related resources (NodePool, NodeClaim, EC2NodeClass) are using the correct API versions after the upgrade.
-
Ensure that your Karpenter version is compatible with the EKS version you're upgrading to. You might need to upgrade Karpenter first before upgrading EKS.
If you've already taken these steps and are still encountering issues, it might be helpful to review the detailed upgrade steps in the Karpenter v1 migration documentation. The upgrade process can be complex, and it's important to follow each step carefully to ensure compatibility between Karpenter and your EKS cluster.
Remember that Karpenter is an open-source project, and while AWS provides support for unmodified versions used with compatible EKS clusters, you are responsible for its installation, configuration, and management in your Kubernetes clusters.
Sources
Announcing Karpenter 1.0 | Containers
Announcing Karpenter 1.0 - AWS
Scale cluster compute with Karpenter and Cluster Autoscaler - Amazon EKS
Relevant content
asked 3 years ago
asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
