Migrate from Operator v1.11 -> v1.13 / v1.14 / v1.15

MongoDB Percona Operator for MongoDB
1

Hello

There is a problem with 1.11 and 1.12 regarding wrong version of PodDisruptionBudget when already on GKE 1.30 (or such).

Is it possible to update from 1.11 directly to 1.13 or 1.14 or 1.15 ?

Thanks & Regards

2

@jamoser it is not something we usually recommend, but we have users who did that and it worked. The problem is with assessing the impact on all the moving parts.
Of course do some tests before the upgrade in non-prod environment, take all the necessary backups.

1 Like
3

Thanks.

Skipping 1 or 2 version seems to work. But a “full” restart is recommended.

4

@jamoser can you share more? What does it mean full restart? Pause/start the cluster?

I’m asking for the sake of the community :slight_smile: