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

support for etcd v3 #15

Open
ploef opened this issue Nov 5, 2016 · 10 comments
Open

support for etcd v3 #15

ploef opened this issue Nov 5, 2016 · 10 comments

Comments

@ploef
Copy link

ploef commented Nov 5, 2016

Hi,

Are there any plans for supporting etcd v3?

Kind regards,
Peter

@ake-persson
Copy link
Owner

I could look into it, may I ask what is your main use-case for using etcdtool. Also do you have suggestions for improvements?

@ploef
Copy link
Author

ploef commented Nov 5, 2016

I think that would be great. As I understand it, etcd v3 is the version they ask us to use now.
Looking for a way to import configuration files (YAML, from git repository) into etcd I stumbled upon etcdtool. As far as I know it's the only tool that makes this possible.

@ake-persson
Copy link
Owner

I'm not sure how useful import/export JSON/YAML/TOML is for etcd v3, since it doesn't support nested nodes anymore i.e. it's a flat key/value store.

You could simulate a nested structure with a separator, but I'm not sure this make's much sense.

I think the only functionality that would make any sense for v3 is maybe export/import.

@ipfaffy
Copy link

ipfaffy commented Apr 7, 2017

+1- I'd love to use this in conjunction with etcd-operators in kubernetes to backup both etcdv2 and etcdv3.

@eiselesr
Copy link

eiselesr commented Dec 6, 2017

Does import/export work with etcd3? I was trying it out and it appears to post using the v2 data store.
I want to be able to batch add keys and values from a generated configuration file. Is there a better way to do this?

@ake-persson
Copy link
Owner

ake-persson commented Dec 6, 2017

Ftm moment I haven't implemented v3 since it flattened the namespace and you can't really import/export a nested structure anymore. You can simulate it thought using a (dot) notation like:

/sub1/
    sub2/
        my-key

To either:

.sub1.sub2.key: value
/sub1/sub2/key: value

Not sure how use-full that would be thought.

As for adding single key with a config in it like JSON/YAML you can do that with etcdctl.

@ake-persson
Copy link
Owner

Suggestions as how to handle this is welcome either use a flat name space for import/export in etcdv3 or simulate a nested one.

@foxdalas
Copy link

@cliang57
Copy link

I am still looking for a good tool to backup and restore etcd v3. Do you still have the plan or is there any good alternative tools to recommend?

@ake-persson
Copy link
Owner

I'm planning on supporting etcdv3, I started prototyping a backend that can support etcd v2/v3. https://github.com/mickep76/kvstore

Atm. for etcdv3 there are some options included in the tools themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants