GCE machine actuator should collect current state

[rsdcastro]

From @jessicaochen on January 11, 2018 17:8

The machine actuator should get current state from the actual sources (eg. kubelet version from machine, VM info from gce) instead of a cached last-applied state. This will help with cases like the state changing under the covers.

https://github.com/kubernetes/kube-deploy/blob/master/cluster-api-gcp/cloud/google/instancestatus.go#L13

Copied from original issue: kubernetes-retired/kube-deploy#482

[rsdcastro]

From @karan on January 24, 2018 21:41

I'll start working on this, and handle updates to spec.providerConfig first. Specifically, zone, machineType, and image.

[karan]

/assign @mkjelland

since she's working on the gce provider now.

[karan]

/unassign @karan

[mkjelland]

/assign @mkjelland

[roberthbailey]

This issue was moved to kubernetes-sigs/cluster-api-provider-gcp#20