Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Deis update engine #2106

Closed
gabrtv opened this issue Oct 10, 2014 · 3 comments
Closed

Deis update engine #2106

gabrtv opened this issue Oct 10, 2014 · 3 comments

Comments

@gabrtv
Copy link
Member

gabrtv commented Oct 10, 2014

Deis update engine is based on CoreUpdate and will ultimately provide fast, painless, zero-downtime upgrades of the platform control plane.

@gabrtv gabrtv self-assigned this Oct 10, 2014
@gabrtv gabrtv added this to the 0.14 milestone Oct 10, 2014
@gabrtv gabrtv removed this from the 0.14 milestone Oct 20, 2014
@carmstrong carmstrong added this to the v1.8 milestone Jun 7, 2015
@carmstrong carmstrong modified the milestones: v1.9, v1.8 Jun 7, 2015
@carmstrong carmstrong modified the milestones: v1.10, v1.9 Jul 1, 2015
@carmstrong carmstrong modified the milestone: v1.10 Jul 29, 2015
@iancoffey
Copy link
Contributor

This should use the upgrade-prep and upgrade-takeover functionality in deisctl, and the CoreOS omaha server on the other end. It should ship as a unit, and be probably be initially disabled by default until it is mature.

Related:
https://coreos.com/docs/coreupdate/custom-apps/coreupdate-protocol/

@bacongobbler
Copy link
Member

Is this something we still want to tackle in terms of v2? I think this is going to be solved in later versions of helm from what I've heard.

@bacongobbler
Copy link
Member

This is not something we'll be able to get to for the LTS release (#4776), and provisioning Deis v2 is done through installing a vanilla kubernetes cluster so I'm going to go ahead and close this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants