Add preemptible as an option to node config (hashicorp#341)

* Add preemptible as an option to node config * Check for preemptible in test matching functions * Move flattenClusterNodeConfig to node_config * Handle bools properly when comparing in cluster and node pool tests * Use a supported image_type in cluster tests
chrisst · Sep 1, 2017 · 6e6a8d8 · 6e6a8d8
1 parent 58293de
commit 6e6a8d8
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/docs/r/container_cluster.html.markdown b/docs/r/container_cluster.html.markdown
@@ -153,6 +153,10 @@ which the cluster's instances are launched
 * `tags` - (Optional) The list of instance tags applied to all nodes. Tags are used to identify 
     valid sources or targets for network firewalls.
 
+* `preemptible` - (Optional) A boolean that represents whether or not the underlying node VMs
+    are preemptible. See the [official documentation](https://cloud.google.com/container-engine/docs/preemptible-vm)
+    for more information. Defaults to false.
+
 **Addons Config** supports the following addons:
 
 * `http_load_balancing` - (Optional) The status of the HTTP Load Balancing

diff --git a/docs/r/container_node_pool.html.markdown b/docs/r/container_node_pool.html.markdown
@@ -105,6 +105,10 @@ resource "google_container_cluster" "primary" {
 
 * `image_type` - (Optional) The image type to use for this node.
 
+* `preemptible` - (Optional) A boolean that represents whether or not the underlying node VMs
+    are preemptible. See the [official documentation](https://cloud.google.com/container-engine/docs/preemptible-vm)
+    for more information. Defaults to false.
+
 The `autoscaling` block supports:
 
 * `minNodeCount` - (Required) Minimum number of nodes in the NodePool. Must be >=1 and