-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
machine-controller: update Machine.Status when appropriate #9
Comments
From @fejta-bot on February 7, 2018 16:32 Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
From @karan on February 7, 2018 17:21 From what I understand we are not going to be using Status. @jessicaochen - please reopen if you think there is a future use for Status. |
From @karan on February 7, 2018 17:21 /close |
From @jessicaochen on February 7, 2018 18:4 Let's make this issue more clear, we should make sure that the Ready & LastUpdated field on the MachineStatus is getting updated by the machine controller. (Or removed from the status if it does not add value) I know that the NodeRef and error messages are already being populated. |
/remove-lifecycle stale |
…s-sigs#250) - Adds new field vsphereCredentialSecret that can be specified to point to the secret that holds the credentials Resolves kubernetes-sigs#9 Change-Id: I8e43864302a51386f7f11725b0a966cc9e436c59
…anch-release-1.0 Add status.version to list of fields to ignore for update
Mark etcd machine status to running after etcd controller adds the etcd machine ready label
From @pipejakob on November 7, 2017 20:8
So far, it doesn't update the Machine's Status at all.
Copied from original issue: kubernetes-retired/kube-deploy#349
The text was updated successfully, but these errors were encountered: