-
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
[Issue-7148] Legacyetcd support for Digital Ocean #7221
[Issue-7148] Legacyetcd support for Digital Ocean #7221
Conversation
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 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. |
/ok-to-test |
...s/cloudup/resources/addons/digitalocean-cloud-controller.addons.k8s.io/k8s-1.8.yaml.template
Show resolved
Hide resolved
Thanks for this! One suggestion about only changing the TTL for DO, if we can avoid it, but otherwise it looks good. I think you need to run |
Sure, will make the change. |
@justinsb - On the same note, I will be working on supporting etcd-manager for DO in the next coming days. I intend to make changes to the etcd-manager repository to support DO cloud provider. Please let me know if this direction sounds Ok. Or you suggest any other alternatives? FYI - @timoreimann |
@justinsb @andrewsykim - Incorporated review comments, please have a look and /approve if you are Ok. |
@srikiz can you squash commits please? |
update template Update notes for digital ocean Update TTL to 60 seconds and version upgrade to 0.1.15 for DO Cloud Controller Manager Update review comments Format go code
0dadc65
to
6392725
Compare
Done @andrewsykim - please have a look when you get a chance. |
@srikiz I released CCM v0.1.16 yesterday. Do you think we could still squeeze that in? Updating should be as simple as bumping the version in the manifest. Nothing else has changed. If you'd like to punt this to a future PR, I'm also fine with that. |
LGTM - thanks for fixing the TTL issue! Can we bump the c-c-m version separately - should be an easy PR to review! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, 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 |
Followed up with #7293 to update the CCM version to v0.1.16. |
Cherry pick of #7221 onto release-1.14
Couple of updates to get digitial ocean cloud provider working with the latest master.
Updated the digital ocean cloud manager to an updated version - 0.1.15
Update KOPS_FEATURE_FLAGS to also include an override flag, this is temporary, I'll be adding the next set of changes to include support for etcd-manager, but until then we can use legacy support.
Update etcd manager for DO cloud provider, so we don't get a not supported error. will be adding another PR for more changes to the etcdmanager repo to support DO.
Note: I have tested this change and it seems to work on release-1.12, release-1.13 and release-1.14 branches. I believe there is some issue with the latest master, I didn't see any logs generated in the master linux server once I SSH to it. If this gets approved, I would like to cherry pick this into release-1.13 or release-1.14 based on your suggestion.