update milestone of open issues marked 0.6.1 to a future or 0.6.2

[raoofm]

Noticed that v0.6.1 is released. Was expecting the issues marked with milestone to be fixed but doesn't seem like.

Can they please be updated with a future milestone, say 0.6.2?
Also #1261

Was specifically looking for #1396, #1051(related to #1416) in the upcoming release, not sure about your priorities.

[hongchaodeng]

Sorry my fault. I put milestones but realized later we needed to work on something else due to company roadmap. We need to come up with a way to make this more public and better communicated.

Can they please be updated with a future milestone, say 0.6.2?

We are releasing 0.7.0 for next. Need to decouple backup, restore spec.
With all those hard changes, we can minimize EtcdCluster's interfaces learnt from past lessons and move towards the stable roadmap.

Was specifically looking for #1396, #1051(related to #1416) in the upcoming release, not sure about your priorities.

Yes. etcd auth, etcd version to 3.2, k8s version to 1.8 is on roadmap.
And please help with those issues :)

[raoofm]

I put milestones but realized later we needed to work on something else due to company roadmap.

Sure it makes sense.

We are releasing 0.7.0 for next. Need to decouple backup, restore spec.
With all those hard changes, we can minimize EtcdCluster's interfaces learnt from past lessons and move towards the stable roadmap

Perfect. Noticed those changes for the past few days via commits 👍

Yes. etcd auth, etcd version to 3.2, k8s version to 1.8 is on roadmap.
And please help with those issues :)

Sure, excited as our cluster is 1.8 too

[hongchaodeng]

Closing this right now as all issues reported here are tracked in other issues and better converge discussion to them:

• etcd 3.2: v3.2.x compatibility? #1396, *: make default etcd version to 3.2.10 #1607
• etcd auth: enabling auth not supported #1051, cannot turn off client cert auth in etcd using v0.5.2 and v3.1.10 #1416
• k8s 1.8: Stress testing against k8s 1.8 #1444