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

• src/versions.tf: Updated the version constraint for the aws provider to >= 4.9.0, < 6.0.0 to ensure compatibility with future versions while avoiding potential breaking changes in version 6.0.0.

Summary by CodeRabbit

• Chores
  • Updated AWS provider version constraints to allow only versions between 4.9.0 (inclusive) and 6.0.0 (exclusive) for improved compatibility.
  • Upgraded the version of the "eks/karpenter-controller" component to enhance system reliability.

why

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

why

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

why

• Support auto merge PRs
• Create merge queue
• Implement new CodeOwners policy

why

• Support auto merge PRs
• Create merge queue
• Implement new CodeOwners policy

You can trigger a rebase of this PR by commenting @dependabot rebase.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Release Notes

• Kubernetes API modifies taints dynamically.
• computed_fields explicitly marks taints as managed by Kubernetes, preventing Terraform from tracking changes while still allowing updates.
• Avoids Terraform drift issues without completely ignoring changes via ignore_changes.
• Ensures Karpenter can dynamically manage taints without Terraform interfering.
• This change addresses the following drift:

 # kubernetes_manifest.node_pool["atomic-low-disk-io"] will be updated in-place
  ~ resource "kubernetes_manifest" "node_pool" {
      ~ object   = {
          ~ spec       = {
              ~ template   = {
                  ~ spec     = {
                      ~ taints        = [
                            {
                                effect    = "NoSchedule"
                                key       = "test.co/atomic-tasks"
                                timeAdded = null
                                value     = "short"
                            },
                          ~ {
                              + value     = (known after apply)
                                # (3 unchanged attributes hidden)
                            },
                        ]
                        # (5 unchanged attributes hidden)
                    }
                    # (1 unchanged attribute hidden)
                }
                # (3 unchanged attributes hidden)
            }
            # (3 unchanged attributes hidden)
        }
        # (1 unchanged attribute hidden)
    }

[!IMPORTANT]
The first apply after this change will show resources being added to state before no changes are detected in future runs

What

• Added computed_fields attribute to the kubernetes_manifest resource to mark spec.template.spec.taints as managed by Kubernetes, which helps avoid continual drift detection.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Usage

atmos terraform plan eks/karpenter-node-pool -s <stack>

Testing

• Validated with atmos validate stacks
• Performed successful atmos terraform apply on component

References

• Manifest Changes Issue

Summary by CodeRabbit

• New Features
  • Introduced a new configuration enhancement for Kubernetes-managed resources that improves drift detection by automatically aligning taint settings with Kubernetes’ control. This update offers a more predictable and stable deployment experience.

why

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

Why

• Test basic component features
• Verify that the component does not create any resources when input enabled: false set
• Verify that the component does not drift on a second run with the same inputs
• Add test for any additional than basic use cases for the component

References

• Component test writing guide
• List of component tests are done

Summary by CodeRabbit

• Refactor

  • Streamlined infrastructure role assignment to simplify deployment logic.

• New Features

  • Introduced several new configuration files enhancing cloud infrastructure management for clusters, node pools, networking, and vendor integrations.
  • Added a flexible CLI configuration for customized deployments.

• Tests

  • Launched an expanded test suite to validate deployment behavior and resource provisioning.

• Chores

  • Upgraded remote state versions, improved dependency management, updated ignore rules, and removed an obsolete test script.

why

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