Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

GCE machine actuator should collect current state #482

Closed
jessicaochen opened this issue Jan 11, 2018 · 2 comments
Closed

GCE machine actuator should collect current state #482

jessicaochen opened this issue Jan 11, 2018 · 2 comments
Assignees
@karan
Labels
cluster-api-gcp
Milestone
cluster-api-alpha...

Comments

@jessicaochen
Copy link
Contributor

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
@karan
Copy link
Contributor

karan commented Jan 24, 2018 •
edited

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

This was referenced Jan 26, 2018
Closed
Merged
@rsdcastro rsdcastro added this to the cluster-api-alpha milestone Feb 2, 2018
@rsdcastro rsdcastro mentioned this issue Apr 17, 2018
Closed
@rsdcastro
Copy link

This issue was moved to kubernetes-sigs/cluster-api#99

@roberthbailey roberthbailey mentioned this issue Jul 24, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@karan karan

Labels
cluster-api-gcp
Projects
None yet
Milestone
cluster-api-alpha-implementation
Development

No branches or pull requests
3 participants
@rsdcastro @karan @jessicaochen