SchwarzIT / terraform-provider-stackit

Community-maintained STACKIT Terraform provider
Apache License 2.0
18 stars 6 forks source link

Terraform stackit_kubernetes_cluster - removes cluster even though only acl was changed #180

Closed Henning1919 closed 1 year ago

Henning1919 commented 1 year ago

Hello,

we are currently implementing a Azure Dev Ops Pipeline that will create us STAKCIT SKE Clusters.

We have noticed that the SKE Modul will replace the whole SKE Cluster even though we only had a ACL Change:

module.ske.stackit_kubernetes_cluster.ske: Refreshing state... [id=adfresh-s]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: -/+ destroy and then create replacement

Terraform will perform the following actions:

module.ske.stackit_kubernetes_cluster.ske must be replaced

-/+ resource "stackit_kubernetes_cluster" "ske" { ~ extensions = { ~ acl = { ~ allowed_cidrs = [

(1 unchanged element hidden)

                "193.148.188.0/24",
              - "10.201.130.0/24",
            ]
            # (1 unchanged attribute hidden)
        }
    }
  ~ id                          = "adfresh-s" -> (known after apply)
  ~ kube_config                 = (sensitive value)
  ~ kubernetes_project_id       = "b93731dd-9187-4769-9c43-1cfd7e544221" # forces replacement -> (known after apply) # forces replacement
  ~ kubernetes_version_used     = "1.25.12" -> (known after apply)
    name                        = "adfresh-s"
    # (3 unchanged attributes hidden)
}

Plan: 1 to add, 0 to change, 1 to destroy.

As you can see the SKE CLuster is beeing replaced even though everything was the same except the ACL

Can you check that please? Regards Henning

Henning1919 commented 1 year ago

Fixed with STACKIT 1.25.1