Implement snap coherence
Bug #1845559 reported by
Cory Johns
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
Wishlist
|
Cory Johns | ||
Kubernetes Worker Charm |
Fix Released
|
Wishlist
|
Cory Johns | ||
Snap Layer |
Fix Released
|
Undecided
|
Cory Johns |
Bug Description
Snapd now supports cohorts (https:/
* The leader of the master should take the cohort snapshots and then provide that to the other master (if any) and workers
* The masters should upgrade before the workers
* Because the cohort snapshot does not change the channel and refreshing to a new snapshot will only refresh point releases, there is no need for it to involve manual intervention
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
Changed in layer-snap: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Added the snap layer because the support for cohort management should be available to all charms.