Gateway enabled cluster recreated on every apply.

[grommir]

Hi there,

I tried to create kubernetes cluster with "gateway_enabled".
Cluster created correctly but on next "terraform apply" it forces recreation.
Looks like terraform won't see "public_vlan_id" for such cluster.

Terraform Version

Terraform v0.12.28

• provider.ibm v1.8.1

Affected Resource(s)

• ibm_container_cluster

Terraform Configuration Files

provider "ibm" {}

variable "hardware_type" { default = "shared" }
variable "dal10_public_vlan" { default = "k8s-dal10.1pub-prod" }
variable "dal10_private_vlan" { default = "k8s-dal10.1priv-prod" }
variable "resource_group" { default = "test" }
variable "cluster_name" { default = "gateway-test-cluster" }

# gather data
data "ibm_network_vlan" "dal10_public_vlan" {
    name = var.dal10_public_vlan
}
data "ibm_network_vlan" "dal10_private_vlan" {
    name = var.dal10_private_vlan
}
data ibm_resource_group "resource_group" {
    name = var.resource_group
}
# create cluster
resource ibm_container_cluster "cluster" {
    name                        = var.cluster_name
    datacenter                  = "dal10"
    machine_type                = "u3c.2x4"
    hardware                    = var.hardware_type
    public_vlan_id              = data.ibm_network_vlan.dal10_public_vlan.id
    private_vlan_id             = data.ibm_network_vlan.dal10_private_vlan.id
    default_pool_size           = 1
    public_service_endpoint     = "true"
    private_service_endpoint    = "true"
    resource_group_id           = data.ibm_resource_group.resource_group.id
    gateway_enabled             = "true"
}

Expected Behavior

No changes. Infrastructure is up-to-date.

Actual Behavior

---
+ public_vlan_id               = "2906496" # forces replacement
---
Plan: 1 to add, 0 to change, 1 to destroy.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
2. terraform apply

[hkantare]

Fixed in latest release
https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.9.0

[hkantare]

closing the issue