fix:adjust instance_type to avoid ResourceInsufficient case (#1418)

Author: lyu571

tencentcloud/basic_test.go

@@ -684,9 +684,19 @@ data "tencentcloud_vpc_subnets" "subnet" {
   vpc_id = data.tencentcloud_vpc_instances.vpc.instance_list.0.vpc_id
 }
 
+data "tencentcloud_instance_types" "default" {
+	filter {
+	  name   = "zone"
+	  values = [var.default_az]
+	}
+	cpu_core_count = 2
+	exclude_sold_out = true
+}
+
 locals {
   vpc_id = data.tencentcloud_vpc_subnets.subnet.instance_list.0.vpc_id
   subnet_id = data.tencentcloud_vpc_subnets.subnet.instance_list.0.subnet_id
+  scale_instance_type = data.tencentcloud_instance_types.default.instance_types.0.instance_type
 }
 `
 

tencentcloud/resource_tc_kubernetes_scale_worker_test.go

@@ -199,9 +199,6 @@ func testAccCheckTkeScaleWorkerExists(n string) resource.TestCheckFunc {
 const testAccTkeScaleWorkerInstanceBasic = defaultAzVariable + TkeExclusiveNetwork + TkeDataSource + defaultSecurityGroupData
 
 const testAccTkeScaleWorkerInstance string = testAccTkeScaleWorkerInstanceBasic + `
-variable "scale_instance_type" {
-  default = "S2.LARGE8"
-}
 
 resource tencentcloud_kubernetes_scale_worker test_scale {
   cluster_id = local.cluster_id
@@ -219,7 +216,7 @@ resource tencentcloud_kubernetes_scale_worker test_scale {
   worker_config {
     count                      				= 1
     availability_zone          				= var.default_az
-    instance_type              				= var.scale_instance_type
+    instance_type              				= local.scale_instance_type
     subnet_id                  				= local.subnet_id
     system_disk_type           				= "CLOUD_SSD"
     system_disk_size           				= 50