docs: fix up incorrect upgrade advice for 3.5 -> 3.6 upgrade#1117
docs: fix up incorrect upgrade advice for 3.5 -> 3.6 upgrade#1117alam0rt wants to merge 1 commit intoetcd-io:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alam0rt The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @alam0rt. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
| Is it possible that custom data exists in v2store despite v2store not being enabled. Before upgrading to 3.6, make sure that you run the `etcdutl check v2store` utility as it prevent 3.6 running. | ||
| {{% /alert %}} | ||
|
|
||
| 1. If there is data in the v2store that needs to be migrated to the v3store, follow the [v2 migration guide](../../../v3.4/op-guide/v2-migration/) to migrate the data. |
There was a problem hiding this comment.
Not sure if this is recommended since we'd need to downgrade to 3.4 right?
Signed-off-by: alam0rt <sam@samlockart.com>
|
|
||
| If `--enable-v2` or the environment variable `ETCD_ENABLE_V2="true"` **is** configured, additional steps are required to handle the v2store data: | ||
| {{% alert title="Important" color="warning" %}} | ||
| Is it possible that custom data exists in v2store despite v2store not being enabled. Before upgrading to 3.6, make sure that you run the `etcdutl check v2store` utility as it prevent 3.6 running. |
There was a problem hiding this comment.
I know this is true because I am experiencing it as we speak haha. Stuck on 3.5 with v2store data. Compounded by not being able to tolerate downtime + v2 API not being accessible etcd-io/etcd#21249
There was a problem hiding this comment.
I think we need to understand the issue you're hitting better, because all of the v2store data issues were supposed to be fixed.
|
/ok-to-test |
|
/retest |
|
@alam0rt Yes, this sounds more like a bug than a required doc change. Let's put this on hold until the bug is evaluated. /hold |
4 participants
It is not true that
*NOTE:** If the --enable-v2 flag is not configured or is set to false, no further action is required.. V2 Store data will continue to be propagated to followers if it exists.