1.12.0 - is it still possible to upgrade as for ex. 1.10.0 -> 1.11.0

1.10.0 → 1.11.0 : no down time
1.11.0 → 1.12.0 : seems down time is required since the config in cr.yaml has changed ?

1 Like

@jamoser Do you have any problems with 1.12.0? We change cr.yaml for each release. So, we have two steps in the update process. The first step is to update the operator and the second one is to update psmdb cluster itself by applying a new CR. The second step always causes the restart of psmdb cluster. Only one thing is different in this release and it is CR validation.

1 Like

@jamoser please tell me more about the problem with downtime and upgrade. Our upgrade process is similar and no downtime is required.

Maybe you could walk me through how you upgrade from 1.10 to 1.11 vs 1.11 to 1.12 ?

1 Like

@all - thanks. My concern is that if we apply the 1.12 cr,yaml then we would have at some point “pod rs1 = 1.11” and “pod rs2 = 1.12”. The question is, if this is working.

Or if I have to set pause=true, apply 1.11 cr.yaml, then apply 1.12 cr.yaml

1 Like

@jamoser Please use our official upgrade documentation to update your cluster. As you can see it is not needed to use any pause option. P.S. As usual I suggest testing a new version (and upgrade itself) on testing env and only after that update a production one.

2 Likes