`azurerm_kubernetes_cluster_node_pool` - `node_count`, `min_node`, and `max_node` can now be set to `0`#8300

Merged

mbfrahry merged 14 commits intohashicorp:masterfrom zeroX-tj:update-min-node-count-validation

Oct 5, 2020

+63-22

Commits on Aug 26, 2020

Update min required value of node_count and min_count
Tim Janssens
committed
Also check equal or higher on combination with autoscaler
Tim Janssens
committed

Commits on Sep 18, 2020

Add test to create zero size nodepool with autoscaling
Tim Janssens
committed
replace tabs by spaces
Tim Janssens
committed
Also remove check in updating nodepool for 0 size
Tim Janssens
committed

Commits on Sep 28, 2020

max_count validation should also start from 0
Tim Janssens
committed
max_count should be higher or equal to min_count
Tim Janssens
committed
Revert "max_count should be higher or equal to min_count"
Tim Janssens
committed
max_count should be higher or equal to min_count => the right way
Tim Janssens
committed
Set min, max and node count to 0 to reflect changes in documentation
Tim Janssens
committed
max_count should be higher or equal to min_count => fixed if statement
Tim Janssens
committed
Revert "max_count should be higher or equal to min_count => fixed if statement"
Tim Janssens
committed
Missed a spot in the documentation
Tim Janssens
committed

Commits on Oct 5, 2020

Update kubernetes_cluster_node_pool_resource.go
mbfrahry
authored