Stuart Sandine dc80787c18 Docs update: container_node_pool allows min_node_count of zero (#3001) ... I was pleasantly surprised to find that it works ok to set `min_node_count` to zero. But the docs say it must be at least one, so this PR proposes a tweak to update that. More context, from https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler: > Beginning with Kubernetes version 1.7, you can specify a minimum size of zero for your node pool. This allows your node pool to scale down completely if the instances within aren't required to run your workloads. However, while a node pool can scale to a zero size, the overall cluster size does not scale down to zero nodes (as at least one node is always required to run system Pods).		2019-03-07 08:59:09 -08:00
..
d	Documentation: fixed TF syntax in google_iam_policy example (#3083)	2019-03-07 08:55:36 -08:00
r	Docs update: container_node_pool allows min_node_count of zero (#3001)	2019-03-07 08:59:09 -08:00
getting_started.html.markdown	Refresh provider docs in anticipation of 2.0.0 (#2981)	2019-02-01 13:26:59 -08:00
index.html.markdown	Refresh provider docs in anticipation of 2.0.0 (#2981)	2019-02-01 13:26:59 -08:00
provider_reference.html.markdown	Update the 2.0.0 Upgrade Guide, misc. other docs (#3031)	2019-02-11 15:24:23 -08:00
provider_versions.html.markdown	Refresh provider docs in anticipation of 2.0.0 (#2981)	2019-02-01 13:26:59 -08:00
version_2_upgrade.html.markdown	Add Bigtable column_family to the upgrade guide (#3054)	2019-02-15 10:20:53 -08:00