SKE Cluster os_version_min not working during creation of resource

[PeterStolz]

Hi, I am trying to create a SKE Cluster using the recently added os_version_min. However the terraform apply fails with the following error message:

╷
│ Error: Error creating/updating cluster
│ 
│   with stackit_ske_cluster.ske,
│   on main.tf line 131, in resource "stackit_ske_cluster" "ske":
│  131: resource "stackit_ske_cluster" "ske" {
│ 
│ Calling API: 400 Bad Request, status code
│ 400, Body:
│ {"code":"InvalidArgument","message":"1 error
│ occurred:\n\t* invalid input: nodepoolName
│ \"np-example\": machine image version
│ \"3815.2.1\" is not available. Supported:
│ [\"3815.2.3\"], Preview
│ [\"3815.2.5\"]\n\n","details":""}
│ 
╵

I would expect this to still create the cluster with the currently supported os version based on the argument name. It works fine with an existing cluster that was upgraded, but I assume during creation the os version is used as a literal.

resource "stackit_ske_cluster" "ske" {
  project_id             = var.stackit_project_id
  name                   = "keycloak"
  kubernetes_version_min = "1.27"
  node_pools = [
    {
      name               = "np-example"
      machine_type       = "g1.3"
      os_version_min     = "3815.2.1"
      minimum            = "2"
      maximum            = "3"
      availability_zones = ["eu01-3"]
      volume_size        = 100
      volume_type        = "storage_premium_perf4"
    }
  ]
  maintenance = {
    enable_kubernetes_version_updates    = true
    enable_machine_image_version_updates = true
    start                                = "01:00:00Z"
    end                                  = "02:00:00Z"
  }
  extensions = {
    argus = {
      enabled           = true
      argus_instance_id = stackit_argus_instance.argus.instance_id
    }
  }
}

I am running the latest provider 0.24.2 Thanks for the help :)

[GokceGK]

Hi @PeterStolz,

thanks for reporting the issue. I will verify this and get back in touch with you.

[GokceGK]

Hi @PeterStolz,

We checked the current implementation and your suggestion. This will be an enhancement in the current implementation. We have created a work item and will address it soon.