[QUESTION] VPC extension causes eks addon upgrade

[laserpedro]

Description

I am current using the terraform-aws-vpc module to create the public subnets and the private subnets for my EKS cluster. I am currently trying to resize the VPC to add more IPs to the public subnets by adding another CIDR range to the secondary cidr range and creating new public subnets from this cidr range that I pass to the var public_subnets. I would like to know the next step once this vpc resizing is done.

The plan from the vpc module is consistent to me, the plan from the eks modules is more strange to me:

~ resource "aws_eks_addon" "this" {
    ~ addon_version               = "v1.3.4-eksbuild.1" -> (known after apply)
      id                          = "iter-dev:eks-pod-identity-agent"
      tags                        = {}
      # (11 unchanged attributes hidden)

      # (1 unchanged block hidden)
  }

And I can see this upgraded for all the AWS addons.

Versions

• Module version [Required]: version = "~> 20.24.0"

• Terraform version:
  1.9.5

• Provider version(s):
  5.62.0

Steps to reproduce the behavior:

Expected behavior

Actually

Actual behavior

Terminal Output Screenshot(s)

Additional context

[laserpedro]

My interpretation is that since the cluster is updated (for its vpc config) the addons are updated and the version of the addons cannot be known at plan time, ok got it.

[laserpedro]

However that can be confusing and in my case I ll test the vpc extension on a new cluster to see the impact.