DB clusters not upgradeable to next major version?

[telderfts]

I have been looking for this in the Everest documentation with no success and it seems like it isn’t editable from the GUI, but how does one go about upgrading their MongoDB cluster once it is running in Everest? Postgres and MySQL give the options of upgrading but it doesn't appear that is available for MongoDB even though the operator allows for it.

[telderfts]

Found that you can update MongoDB but only within the version that you are running. So if you are running a low version of 5.x you can only move to the highest minor version of 5.x, same with 6.x, etc. Huge problem since Mongo seems to deprecate an older version every 8-12 months.

[telderfts]

Changed the title for this since it appears to affect ALL of the DB Engines, not just MongoDB. Tried with Postgres and can only upgrade inside of a particular version, can't go to the next major version. This will prevent us and probably others from rolling Everest out in larger environments outside of a developer only testing platform.

[recharte]

Hi @telderfts this is already in our roadmap (EVEREST-1111)
We currently have no blockers for implementing it for MongoDB.
For PostgreSQL however, Percona's PostgreSQL Operator still has this feature in technical preview so it might take a little bit more time until we release PostgreSQL major version upgrades in Everest.

[telderfts]

@recharte Appreciate the quick response, is this already implemented for MySQL as well?

[hors]

Hi @telderfts We do not support major MySQL updates in operators based on PXC. This was a product/design decision, and we do not plan to add it in the near future.

[telderfts]

@hors I did not know that, thanks for that info. If we there was a way to get this implemented for Mongo and work towards getting it implemented for Postgresql that would be great since companies need to be able to stay on upgrade paths and cadences.