etcd 3.2 works with Kubernetes 1.18 but not 1.19
Bug #1913227 reported by
James Troup
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Etcd Charm |
Fix Released
|
High
|
George Kraft |
Bug Description
We followed the CDK 1.18 -> 1.19 upgrade documentation available here:
https:/
At the end of the process, we were still on etcd 3.2, but it was not working reliably with Kubernetes 1.19 - etcd was crashing a lot with backtraces. Either this is a bug in 3.2 which should be fixed, and/or our documentation should explicitly tell you to upgrade to 3.4.
Changed in charm-etcd: | |
importance: | Undecided → High |
Changed in charm-etcd: | |
status: | New → In Progress |
Changed in charm-etcd: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Subscribing field-high as (I think) this will bite anyone who follows our upgrade docs; if etcd 3.2 is meant to work with Kubernetes 1.19, let me know and I can provide logs.