examples/v2/gke/jinja: update fails about deploymentmanager-samples

[munutzer]

I'm currently working on supporting cluster updates through DM. Estimating one month until more update support is available.

[nfirvine]

This bug:
https://stackoverflow.com/questions/44525692/google-cloud-deployment-manager-update-container-cluster
https://issuetracker.google.com/issues/38131324
No workaround AFAIK

[davidebelloni]

Hi,
I have the same problem

[munutzer]

I have updated the cluster type so that changing the initialNodeCount property in the DM config will resize the node pool. Note that the initialNodeCount property change won't be reflected in the cluster API (initialNodeCount property stores initial, not current size), but you can see the resize by looking at the underlying managed instance group:

$ gcloud deployment-manager deployments create cluster-resize --template https://raw.githubusercontent.com/GoogleCloudPlatform/deploymentmanager-samples/master/examples/v2/gke/jinja/cluster.jinja --properties zone:us-central1-a,initialNodeCount:2

$ gcloud compute instance-groups managed list
NAME LOCATION SCOPE BASE_INSTANCE_NAME SIZE TARGET_SIZE INSTANCE_TEMPLATE AUTOSCALED
gke-cluster-resize-clust-default-pool-05527e5c-grp us-central1-a zone gke-cluster-resize-clust-default-pool-05527e5c 2 2 gke-cluster-resize-clust-default-pool-05527e5c no

$ gcloud deployment-manager deployments update cluster-resize --template https://raw.githubusercontent.com/GoogleCloudPlatform/deploymentmanager-samples/master/examples/v2/gke/jinja/cluster.jinja --properties zone:us-central1-a,initialNodeCount:3

$ gcloud compute instance-groups managed list NAME LOCATION SCOPE BASE_INSTANCE_NAME SIZE TARGET_SIZE INSTANCE_TEMPLATE AUTOSCALED
gke-cluster-resize-clust-default-pool-05527e5c-grp us-central1-a zone gke-cluster-resize-clust-default-pool-05527e5c 3 3 gke-cluster-resize-clust-default-pool-05527e5c no