v0.21.3

What's Changed

• This release introduces the karpenter_ephemeral_volume_size variable, enabling you to specify the ephemeral volume size for EC2 node classes managed by Karpenter. This addition provides greater flexibility in configuring the storage capacity of nodes to meet workload requirements.
  • New Variable: karpenter_ephemeral_volume_size
    Allows you to define the size (in GiB) of ephemeral volumes for EC2 instances managed by Karpenter's NodeClass.
    Default: 50 Gi.
  • Improved Flexibility: Configure node storage to accommodate storage-intensive applications and workload-specific requirements.

by @uchinda-sph in #150

Full Changelog: v0.21.2...v0.21.3

v0.21.2

⚠️ Important Note on Pod Identity and Fargate Profiles ⚠️

• Pod Identity is not supported when using Fargate profiles.
• EBS Controller Pods running on Fargate profiles cannot leverage Pod Identity.
• If you plan to use Pod Identity, ensure that:
  • EKS add-ons and essentials are excluded from Fargate profiles.

Variable Changes

• enable_pod_identity_for_eks_addons: Default value set to false to address issues with EKS add-ons deployed on Fargate profiles.
• karpenter_nodeclasses: Fixed the variable value to ensure proper configuration.

by @uchinda-sph in #149

Full Changelog: v0.21.1...v0.21.2

v0.21.1

What's Changed

• Removal of Karpenter CRD Installation by Manifest: We are removing the option to install Karpenter CRDs via a manifest. This change will streamline the installation process by transitioning to a Helm Installation.

• Dropping Support for Access Entry Migration from AWS Auth Config: Support for automatic migration of access entries from the AWS auth config is being deprecated and removed. Users are now required to manually configure access entries.

Variable Changes

• Removed variables:
  • karpenter_crd_helm_install
  • migrate_aws_auth_to_access_entry

by @uchinda-sph in #148

Full Changelog: v0.21.0...v0.21.1

v0.20.7

What's Changed

• In this release, we are lifting the version lock on Kubernetes 1.30. This means that version 1.30 will no longer be locked or restricted, allowing users to freely update to 1.31 version or apply it in their environments.

Full Changelog: v0.20.6...v0.20.7

v0.21.0

BREAKING CHANGES

• With this change, Karpenter will automatically discover security groups based on the specified tag. By default, it will include security groups that match the tag karpenter.sh/discovery = [cluster_name].
• Ensure that the necessary security groups are updated with the appropriate tags to facilitate this discovery process.

Full Changelog: v0.20.6...v0.21.0

v0.20.6

Bug Fix

• Change the logic of fetching values of iam roles for EKS addons by @uchinda-sph in #144

Full Changelog: v0.20.5...v0.20.6

v0.20.5

What's Changed

• feat: enable pod identity for eks addons by default by @uchinda-sph in #143

Full Changelog: v0.20.4...v0.20.5

v0.20.4

What's Changed

• The cluster_version variable condition is set to ensure that accidental installations or upgrades to version 1.31 are prevented. Some EKS add-ons are still not compatible with version 1.31, and this validation helps enforce that the cluster version remains below 1.31 to avoid potential issues with add-on compatibility.

Full Changelog: v0.20.3...v0.20.4

v0.20.3

Bug Fix

• Update the startupapicheck image of certmanager by @uchinda-sph in #139

Full Changelog: v0.20.2...v0.20.3

v0.20.2

Bug Fix

• Set the variable enable_cluster_creator_admin_permissions to true by default to support newly created clusters. However, during the migration process, this variable should be set to false because EKS itself adds admin records to access entries.

by @uchinda-sph in #138

Full Changelog: v0.20.1...v0.20.2