Support multiple ETCD instances
ntaylor1781 opened this issue · 4 comments
A common Kubernetes use case is to utilize two or more ETCD clusters. Generally this is one for events, and one for the rest of the objects. There are situations where a third is brought in as well (Cilium is an example of this). Currently etcdadm cannot support that workflow on a single host.
This would require a new concept of instance (or cluster), and update logic to specify the one you want to work against. One idea, that would attempt to keep ease of use, would be to utilize config files. For instance, if etcdadm init was called , it could create a config file in /etc/etcdadm with the arguments passed (or the defaults if none were passed). It could use the instance/cluster name as the config file name (using default if none is provided). We would need to ensure that instance/cluster names are unique at time of creation in this example. Further calls that don't specify a config file, could be assumed to be against the default instance/cluster, and would require appropriate warnings/checks to ensure it is the desired cluster.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-contributor-experience at kubernetes/community.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-contributor-experience at kubernetes/community.
/close
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.