-
Notifications
You must be signed in to change notification settings - Fork 717
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
etcd: add flag for checking member data consistency #2676
Comments
See: - etcd-io/etcd#13766 - kubernetes/kubeadm#2676 Signed-off-by: Andrey Smirnov <[email protected]>
Looks like that the flag check doesn't always work but that is the better option until 3.5.3 |
See: - etcd-io/etcd#13766 - kubernetes/kubeadm#2676 Signed-off-by: Andrey Smirnov <[email protected]> (cherry picked from commit ad6b7ec)
kubernetes/kubernetes#109470 was merged for etcd v3.5.3. |
we can backport kubernetes/kubernetes#109471 to 1.21, 1.22, 1.23 |
The current work is done. There may be some work after we upgrade to etcd 4.0(maybe a long time later). See more roadmap at etcd-io/etcd#9190.
|
ack, thanks for the info. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
FWIW, 3.5.11 (default in kubeadm 1.30 currently) does not have the non-experimenta flag yet:
|
etcd-io/etcd#18478 |
xref etcd-io/etcd#13766
announcement of the bug's impact at k-dev:
https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAJs3Yt0WKgyUFL%3D1V13ojZPvV9_Qsa8WXLeohUxhRjEK07P25g%40mail.gmail.com?utm_medium=email&utm_source=footer
(note: the bug in question in relatively rare)
add the etcd flag --experimental-initial-corrupt-check to all kubeadm versions that use etcd 3.5.x by default.
1.24 (master), 1.23, 1.22.
1.24 timeframe
add the --experimental-initial-corrupt-check flag to versions of kubeadm that use etcd
3.5.[0-2]
1.25 timeframe
backport a 3.5.3+ bump to kubeadm versions in support.
aligns with #2567 too.
** future work **
etcd 3.6 (or 4.0?) may graduate the flag / feature to --initial-corrupt-check, thus once we upgrade kubeadm to that etcd version we should switch to the new flag as well.
The text was updated successfully, but these errors were encountered: