This upgrade takes both API versions from v1beta1 to v1 and therefore requires karpenter >= 1

what

• Support Karpenter v1

why

• We should be using the latest version of Karpenter. v1 in karpenter introduced a few changes that we need to handle with the ec2 node class and node pool manifests

references

• https://github.com/cloudposse-terraform-components/aws-eks-karpenter-controller

Summary by CodeRabbit

• New Features

  • Introduced flexible AMI selection for node pools using the new ami_selector_terms field, replacing the previous ami_family approach.
  • Added support for specifying disruption budget reasons in node pool configurations.

• Improvements

  • Updated Karpenter API versions and manifest schemas to align with the latest standards.
  • Enhanced documentation and examples to reflect new configuration options and updated URLs.
  • Increased AWS provider version constraint for improved compatibility.
  • Upgraded component and Helm chart versions for dependencies.

• Bug Fixes

  • Minor formatting and indentation corrections in documentation and configuration files.

why

To have most recent changes of README.md and doc from origin templates