-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Spotinst: Rolling update always reports NeedsUpdate #7251
Spotinst: Rolling update always reports NeedsUpdate #7251
Conversation
Hi @liranp. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
bc003f5
to
ff58f4a
Compare
/ok-to-test |
Thanks @liranp . Seems like a pragmatic approach! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, liranp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The instance registration registers all active instances with their instance group. In addition, it looks for outdated instances by comparing each instance creation timestamp against the modification timestamp of its instance group.
In a rolling-update operation, one or more detach operations are performed to replace existing instances. This is done by updating the instance group and results in updating the modification timestamp to the current time. The update of the modification timestamp occurs only after the detach operation is completed, meaning that new instances have already been created, so our comparison may be incorrect.
In order to work around this issue, we assume that the detach operation will take up to two minutes, and therefore we subtract this duration from the modification timestamp of the instance group before the comparison.