Skip to content
This repository has been archived by the owner on Mar 28, 2020. It is now read-only.

v3.2.x compatibility? #1396

Closed
bmcustodio opened this issue Sep 12, 2017 · 7 comments · Fixed by #1607
Closed

v3.2.x compatibility? #1396

bmcustodio opened this issue Sep 12, 2017 · 7 comments · Fixed by #1607
Milestone

Comments

@bmcustodio
Copy link
Contributor

Is v3.2.x supported? Are there any known issues? I've seen #1222 and #1360, but I see they are fixed now. What is the current status?

@hongchaodeng
Copy link
Member

Not supported yet.
Blocked on issue: #1384

@raoofm
Copy link

raoofm commented Oct 2, 2017

ping ?

@hongchaodeng
Copy link
Member

Moving forward, etcd 3.2+ is definitely preferred.
The requirements on top of my head is to just change the default version and do stress testing on our CI. I will create new jobs to run it later this week.

As a side note, it is appreciated that if you guys can try it and provide more feedback, report any problems you have. Thanks!

@hongchaodeng hongchaodeng added this to the 0.6.1 milestone Oct 3, 2017
@raoofm
Copy link

raoofm commented Oct 3, 2017

#1384 is one issue

@hongchaodeng
Copy link
Member

ref: #1607

@bmcustodio
Copy link
Contributor Author

@hongchaodeng I am facing all the TLS issues described in #1607 in 0.7.0, so IMHO this should not be closed. Is at least etcd 3.2.10 still fully supported by 0.7.0?

@hongchaodeng
Copy link
Member

hongchaodeng commented Nov 25, 2017

@brunomcustodio
See "Milestone". It is fixed in 0.7.1 .

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

Successfully merging a pull request may close this issue.

3 participants