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.

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

[Digital Ocean] Implement Delete Instance logic for rolling update #10000

Merged
merged 4 commits into from
Oct 13, 2020

Conversation

srikiz
Copy link
Contributor

@srikiz srikiz commented Sep 29, 2020

Implement delete instance for handling rolling updates.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 29, 2020
@k8s-ci-robot
Copy link
Contributor

Hi @srikiz. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 29, 2020
@k8s-ci-robot k8s-ci-robot added the area/provider/digitalocean Issues or PRs related to digitalocean provider label Sep 29, 2020
@olemarkus
Copy link
Member

Have a look at #9927
You may want to merge this into your PR so that rolling update does not require running anything in a second terminal. I think this should work fairly out of the box also with DO.

What I do there is basically just run the full update process in-between terminations.

@srikiz
Copy link
Contributor Author

srikiz commented Sep 29, 2020

@olemarkus - Would it be okay if I merge this separately as a new PR once #9927 is merged?

@olemarkus
Copy link
Member

Fine for me :)

@hakman
Copy link
Member

hakman commented Sep 29, 2020

In this case, let's try to get #9927 moving. @zetaab do you have some time to look at it?
/ok-to-test
/hold until #9927 is merged

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 29, 2020
@hakman hakman added this to the v1.19 milestone Sep 29, 2020
@hakman
Copy link
Member

hakman commented Oct 2, 2020

#9927 has been merged.
/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 2, 2020
@srikiz
Copy link
Contributor Author

srikiz commented Oct 6, 2020

/retest

Co-authored-by: Ciprian Hacman <ciprianhacman@gmail.com>
@olemarkus
Copy link
Member

In instancegroups.go there is a function reconcileInstanceGroup(). If you add a check for DO there, rolling updates of DO clusters should work too.

@srikiz
Copy link
Contributor Author

srikiz commented Oct 13, 2020

In instancegroups.go there is a function reconcileInstanceGroup(). If you add a check for DO there, rolling updates of DO clusters should work too.

Okay, I have actually added the check in reconcileInstanceGroup, am I missing something?

@olemarkus
Copy link
Member

Sorry, I must have missed that.
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 13, 2020
@hakman hakman added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Oct 13, 2020
@hakman
Copy link
Member

hakman commented Oct 13, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, srikiz

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2020
@k8s-ci-robot k8s-ci-robot merged commit 4d251fe into kubernetes:master Oct 13, 2020
@srikiz srikiz deleted the DO-Implement-Rolling-Update branch November 24, 2020 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/digitalocean Issues or PRs related to digitalocean provider area/rolling-update cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants