You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| kubernetes\_version | The Kubernetes version of the masters. If set to 'latest' it will pull latest available version in the selected region. | string |`"latest"`| no |
108
107
| logging\_service | The logging service that the cluster should write logs to. Available options include logging.googleapis.com, logging.googleapis.com/kubernetes (beta), and none | string |`"logging.googleapis.com"`| no |
@@ -149,6 +148,7 @@ Then perform the following commands on the root folder:
149
148
| node\_pools\_names | List of node pools names |
150
149
| node\_pools\_versions | List of node pools versions |
151
150
| region | Cluster region |
151
+
| service\_account | The service account to default running nodes as if not overridden in `node_pools`. |
152
152
| type | Cluster type (regional / zonal) |
153
153
| zones | List of zones in which the cluster resides |
154
154
@@ -170,7 +170,7 @@ The [project factory](https://github.com/terraform-google-modules/terraform-goog
In order to execute this module you must have a Service Account with the
@@ -264,6 +264,20 @@ The test-kitchen instances in `test/fixtures/` wrap identically-named examples i
264
264
265
265
Alternatively, you can simply run `make test_integration_docker` to run all the test steps non-interactively.
266
266
267
+
If you wish to parallelize running the test suites, it is also possible to offload the work onto Concourse to run each test suite for you using the command `make test_integration_concourse`. The `.concourse` directory will be created and contain all of the logs from the running test suites.
268
+
269
+
When running tests locally, you will need to use your own test project environment. You can configure your environment by setting all of the following variables:
Each test-kitchen instance is configured with a `variables.tfvars` file in the test fixture directory, e.g. `test/fixtures/node_pool/terraform.tfvars`.
| kubernetes_version | The Kubernetes version of the masters. If set to 'latest' it will pull latest available version in the selected region. | string |`latest`| no |
115
-
| logging_service | The logging service that the cluster should write logs to. Available options include logging.googleapis.com, logging.googleapis.com/kubernetes (beta), and none | string |`logging.googleapis.com`| no |
116
-
| maintenance_start_time | Time window specified for daily maintenance operations in RFC3339 format | string |`05:00`| no |
117
-
| master_authorized_networks_config | The desired configuration options for master authorized networks. Omit the nested cidr_blocks attribute to disallow external access (except the cluster node IPs, which GKE automatically whitelists)<br><br> ### example format ### master_authorized_networks_config = [{ cidr_blocks = [{ cidr_block = "10.0.0.0/8" display_name = "example_network" }], }]| list |`<list>`| no |
118
-
| monitoring_service | The monitoring service that the cluster should write metrics to. Automatically send metrics from pods in the cluster to the Google Cloud Monitoring API. VM metrics will be collected by Google Compute Engine regardless of this setting Available options include monitoring.googleapis.com, monitoring.googleapis.com/kubernetes (beta) and none | string |`monitoring.googleapis.com`| no |
119
-
| name | The name of the cluster (required) | string | - | yes |
120
-
| network | The VPC network to host the cluster in (required) | string | - | yes |
| network_project_id | The project ID of the shared VPC's host (for shared vpc support) | string | `` | no |
123
-
| remove_default_node_pool | Boolean value determining removal of default node pool | bool | false | no |
124
-
| node_pools | List of maps containing node pools | list |`<list>`| no |
125
-
| node_pools_labels | Map of maps containing node labels by node-pool name | map |`<map>`| no |
126
-
| node_pools_metadata | Map of maps containing node metadata by node-pool name | map |`<map>`| no |
127
-
| node_pools_tags | Map of lists containing node network tags by node-pool name | map |`<map>`| no |
128
-
| node_pools_taints | Map of lists containing node taints by node-pool name | map |`<map>`| no |
129
-
| node_version | The Kubernetes version of the node pools. Defaults kubernetes_version (master) variable and can be overridden for individual node pools by setting the `version` key on them. Must be empyty or set the same as master at cluster creation. | string | `` | no |
130
-
| non_masquerade_cidrs | List of strings in CIDR notation that specify the IP address ranges that do not use IP masquerading. | list |`<list>`| no |
131
-
| project_id | The project ID to host the cluster in (required) | string | - | yes |
132
-
| region | The region to host the cluster in (required) | string | - | yes |
133
-
| regional | Whether is a regional cluster (zonal cluster if set false. WARNING: changing this after cluster creation is destructive!) | string |`true`| no |
134
-
| service_account | The service account to default running nodes as if not overridden in `node_pools`. Defaults to the compute engine default service account | string | `` | no |
135
-
| stub_domains | Map of stub domains and their resolvers to forward DNS queries for a certain domain to an external DNS server | map |`<map>`| no |
136
-
| subnetwork | The subnetwork to host the cluster in (required) | string | - | yes |
137
-
| zones | The zones to host the cluster in (optional if regional cluster / required if zonal) | list |`<list>`| no |
138
-
139
-
## Outputs
140
-
141
-
| Name | Description |
142
-
|------|-------------|
143
-
| ca_certificate | Cluster ca certificate (base64 encoded) |
144
-
| endpoint | Cluster endpoint |
145
-
| horizontal_pod_autoscaling_enabled | Whether horizontal pod autoscaling enabled |
@@ -275,6 +212,20 @@ The test-kitchen instances in `test/fixtures/` wrap identically-named examples i
275
212
276
213
Alternatively, you can simply run `make test_integration_docker` to run all the test steps non-interactively.
277
214
215
+
If you wish to parallelize running the test suites, it is also possible to offload the work onto Concourse to run each test suite for you using the command `make test_integration_concourse`. The `.concourse` directory will be created and contain all of the logs from the running test suites.
216
+
217
+
When running tests locally, you will need to use your own test project environment. You can configure your environment by setting all of the following variables:
Each test-kitchen instance is configured with a `variables.tfvars` file in the test fixture directory, e.g. `test/fixtures/node_pool/terraform.tfvars`.
0 commit comments