Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GCP provider: support in-place property updates on the machine #95

Closed
rsdcastro opened this issue Apr 17, 2018 · 1 comment
Closed

GCP provider: support in-place property updates on the machine #95

rsdcastro opened this issue Apr 17, 2018 · 1 comment

Comments

@rsdcastro
Copy link

From @rsdcastro on January 29, 2018 22:22

Copied from original issue: kubernetes-retired/kube-deploy#534
@rsdcastro rsdcastro mentioned this issue Apr 17, 2018
Closed
@roberthbailey
Copy link
Contributor

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

@roberthbailey roberthbailey mentioned this issue Jul 24, 2018
Closed
chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
@k8s-ci-robot
Merge pull request kubernetes-sigs#95 from chuckha/release
2d75357 
Release
chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
@k8s-ci-robot
Merge pull request kubernetes-sigs#95 from SataQiu/fix-20190808
08dafc3 
Refactor: use Patch instead of Update to update a config
jayunit100 pushed a commit to jayunit100/cluster-api that referenced this issue Jan 31, 2020
@sidharthsurana @k8s-ci-robot
Misc fixes (kubernetes-sigs#115)
eeb43e9 
* Updates the wait condition for the worker node to APIStatus
* Fix the kubeadm token caching issue by adding a jitter in the
  re-queue interval
* Fix few minor typos

Resolves kubernetes-sigs#94
Resolves kubernetes-sigs#95

Change-Id: Ic3aaee93f807ebf4fd8ca3964d46510be627c2b2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rsdcastro @roberthbailey