Document for 3.6 release

[ahrtr]

We need to cover the following topics,

• Release blogs

  • Some features: v2store deprecation, downgrade, etc.
  • performance improvement (reduce memory usage):
    • Run a separate in memory snapshot to reduce number of entries stored in raft memory storage etcd#18825
    • Reuse events used for syncing watchers etcd#17563

• Upgrade checklist and guide

  • v2store deprecation: --enable-v2, --experimental-enable-v2v3 and other v2 proxy flags have already been removed in 3.6. Refer to [3.5] Print warning message for deprecated v2 flags if set etcd#18999
    • Users must remove these these flags before upgrading from 3.5 to 3.6. Also refer to Expected v2 deprecation behavior in HA clusters etcd#17009 (comment)
    • Run the tool to ensure there is no custom content in v2store: [3.5] Add offline command to check whether the v2store contains custom content etcd#18993
  • downgrade stuff
  • anything else

• The breaking change on the experimental flag as mentioned in Add server level feature gate etcd#18023 (comment)

• anything else ?

cc @jmhbnz @ivanvc

[jmhbnz]

/assign

[ahrtr]

Some documentation work as mentioned in etcd-io/etcd#18023 (comment)

[shivamgcodes]

Hey @jmhbnz ! I'd like to help write the docs for this release. Could you please point me to some specific actionable tasks I could take on to contribute?

[Zanda256]

Hi @jmhbnz , I would like to put work on this issue.

[jmhbnz]

Hi @shivamgcodes, @Zanda256 - Please feel free to begin writing the upgrade guide for 3.5 to 3.6 similar to https://etcd.io/docs/v3.6/upgrades/upgrade_3_5/

We can start with a basic page covering the upgrade steps which will be similar to 3.5, then we can iterate with additional pull requests to document any breaking changes that users need to be aware of.

[Zanda256]

Hi @shivamgcodes , let's connect on slack.

[shivamgcodes]

Yea , perfect. I sent you a text on slack, pls check

[Zanda256]

I do not see any messages. What is your username in the Kubernetes slack workspace?