Allow transparent rolling restarts of a dotCMS cluster to logged-in, backend users #28532
Open
4 of 8 tasks
Labels
dotCMS : Technical Debt
Dealing with long standing tech debt
dotCMS : Upgrade
Epic
OKR : Cloud Engineering
Owned by Gregg
OKR : Reliability
Owned by Danny
Team : Cloud Eng
Triage
Type : New Functionality
Parent Issue
Epic: support evergreen deployments in dotCMS Cloud #67
User Story
As a dotCMS user, I want upgrades to happen without downtime, so that I can greatly reduce the effort and disruption of getting a new version
As a cloud engineer, I want to be pod updates/changes to be transparent to users, so that I can start doing deployments outside of maintenance windows.
Acceptance Criteria
Proposed Objective
Reliability
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Related
The text was updated successfully, but these errors were encountered: