Upgrade of terraform eks module wants to recreate cluster

[KnHell]

Description

Terraform plan suggests my EKS cluster will be destroyed when upgrading to EKS module v21 despite the documentation stating

bootstrap_self_managed_addons is now hardcoded to false. This is a legacy setting and instead users should utilize the EKS addons API, which is what this module does by default. In conjunction with this change, the bootstrap_self_managed_addons is now ignored by the module to aid in upgrading without disruption (otherwise it would require cluster re-creation).

• [ x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

• Module version [Required]: 21.3.2

• Terraform version: 1.13.3

• Provider version(s):
  aws: v6.20.0
  kubernetes: v2.38.0
  helm: v2.17.0

Reproduction Code [Required]

Keep cluster version but upgrade eks module to v21

Steps to reproduce the behavior:

terraform plan:

module.fins.module.ekscluster.module.eks.aws_eks_cluster.this[0] must be replaced

+/- resource "aws_eks_cluster" "this" {
~ arn = "arn:aws:eks:eu-west-1:1234567890:cluster/clustername" -> (known after apply)
~ bootstrap_self_managed_addons = true -> false
~ certificate_authority = [
- {

Expected behavior

There are no significant changes besides nodes in the nodegroup being upgraded to AL2023. Cluster version not updated. I would expect cluster not being replaced when only upgrading the eks module version

Actual behavior

terraform plan states that the cluster will be destroyed and recreated