Duplicate
Details
Assignee
UnassignedUnassignedReporter
Jordane FillatreJordane FillatreNeeds QA
YesComponents
Affects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Jordane Fillatre
Jordane FillatreNeeds QA
Yes
Components
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created December 21, 2022 at 11:21 AM
Updated December 21, 2022 at 3:25 PM
Resolved December 21, 2022 at 3:25 PM
Hi,
Percona-operator-for-mongodb upgrade documentation separate Operator Manual/Semi automatic update and Percona Server for MongoDB update.
I don't understand how we can deal with Operator upgrade when the SmartUpdate updateStrategy is set. Indeed Operator upgrade talk about upgrade of operator deployment update itself, but it also describe manual or rolling upgrade of mongodb statefulset pods by replacing images in percona mongo CR.
When updateStrategy is set to SmartUpdate, is it a supported way to:
- first upgrade operator, by manually update CRDs, and after update deployment using helm
- update the crVersion of our deployment
- skip images update
- update the upgradeOptions.apply version to trigger Percona Server for MongoDB update using SmartUpdate
Can you clarify that in documentation?
Regards