https://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-07-14T14:55:27ZPulpPulp - Story #7120: As a plugin developer, I have docs that require me to support zero-downtime upgrades and docs explaining how to do sohttps://pulp.plan.io/issues/7120?journal_id=595032020-07-14T14:55:27Zfao89
<ul></ul><p>Talking about "seamless upgrade" from operator, I think one pain we have is plugins requiring different versions of pulpcore.</p>
<p>Let's say I use pulp_file, pulp_container, and pulp_rpm, new pulpcore and pulp_file version are released.
What the operator should do? Only update the pulpcore when all installed plugins support it?</p> Pulp - Story #7120: As a plugin developer, I have docs that require me to support zero-downtime upgrades and docs explaining how to do sohttps://pulp.plan.io/issues/7120?journal_id=595332020-07-15T09:30:34Zmdellweg
<ul></ul><p>Part of the policy should be, that removals (destructive migrations) can only ever happen at major or minor releases.
This would allow that you can always install the latest bugfix release of your current y-release.
Maybe we need to claim that you can only upgrade seemlessly from the latest bugfix to the next minor version.</p> Pulp - Story #7120: As a plugin developer, I have docs that require me to support zero-downtime upgrades and docs explaining how to do sohttps://pulp.plan.io/issues/7120?journal_id=623622020-09-17T13:36:36Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Tags</strong> <i>Documentation</i> added</li></ul> Pulp - Story #7120: As a plugin developer, I have docs that require me to support zero-downtime upgrades and docs explaining how to do sohttps://pulp.plan.io/issues/7120?journal_id=784502022-01-17T13:52:07Zpulpbot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/78450/diff?detail_id=79273">diff</a>)</li><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul>