This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
[WIP] Selfmanaged etcd cluster #629
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Does rolling replacement update on controller ASG, followed by workers Punts on upgrading etcd cluster- simply makes sure resource definitions don't change after create.
…tack This is more of a POC to see if it could be easily done. The code is probably not that clean, Go is not my native language :).
Closed
Closed
|
No discussion happened! i still feel this is a really important component of kube-aws deployments. New work on this has been done in https://github.com/pieterlange/kube-aws/tree/feature/external-etcd. If anyone finds this later, please also refer kubernetes-retired/kube-aws#9 |
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I feel more comfortable managing the cluster state separately from kube-aws. I do not expect this PR to be merged due to code quality 😆 but it does work for my use case and may serve as inspiration for discussion.
There's several reasons for wanting a selfmanaged etcd cluster:
Additionally, as etcd nodes are "outside" of the kube cluster it is more difficult to add logging/monitoring daemons, increasing the risk of catastrophic failure as the nodes themselves are not properly monitored. Yes, i've been hurt before ;-)
(this PR is based on @colhom's
cluster-upgradesbranch)Please discuss! :)