Removed the custom test for create_service_account

I will integrate the test with the workload identity test.

Author: mmontan

.kitchen.yml

@@ -29,13 +29,6 @@ platforms:
   - name: local
 
 suites:
-  - name: "create_service_account"
-    driver:
-      root_module_directory: test/fixtures/create_service_account
-    verifier:
-      systems:
-        - name: create_service_account
-          backend: local
   - name: "deploy_service"
     driver:
       root_module_directory: test/fixtures/deploy_service

examples/create_service_account/README.md

@@ -40,8 +40,9 @@ module "gke" {
   subnetwork              = var.subnetwork
   ip_range_pods           = var.ip_range_pods
   ip_range_services       = var.ip_range_services
-  create_service_account  = false
-  service_account         = var.compute_engine_service_account
+  create_service_account  = true
+  grant_registry_access   = true
+  registry_project_id     = var.registry_project_id
   enable_private_endpoint = true
   enable_private_nodes    = true
   master_ipv4_cidr_block  = "172.16.0.0/28"

examples/create_service_account/main.tf

@@ -48,7 +48,6 @@ variable "ip_range_services" {
   description = "The secondary ip range to use for pods"
 }
 
-variable "compute_engine_service_account" {
-  description = "Service account to associate to the nodes in the cluster"
+variable "registry_project_id" {
+  description = "Project name for the GCR registry"
 }
-

examples/create_service_account/outputs.tf

@@ -25,5 +25,5 @@ module "example" {
   subnetwork                     = google_compute_subnetwork.main.name
   ip_range_pods                  = google_compute_subnetwork.main.secondary_ip_range[0].range_name
   ip_range_services              = google_compute_subnetwork.main.secondary_ip_range[1].range_name
-  compute_engine_service_account = var.compute_engine_service_account
+  registry_project_id = var.registry_project_id
 }