📚 Proposal: Add Upgrade/Migration Documentation Guide

[pratik-mahalle]

Reason/Context

Currently, there's no dedicated documentation page for users upgrading between Microcks versions. Upgrade information is scattered across release blog posts, and users—especially enterprise teams new to Microcks—may not know where to look or whether any action is required when upgrading.

Description

Create a new documentation page at /documentation/guides/administration/upgrading.md that consolidates upgrade guidance.

The page would explain Microcks’ versioning philosophy and compatibility expectations, outline a clear pre-upgrade checklist (backups, release note review, staging tests), and provide step-by-step upgrade instructions for Helm Chart, Kubernetes Operator, and Docker/Podman Compose deployments.

Placement rationale: /documentation/guides/administration/ is the natural home, alongside related admin topics like users, secrets, and snapshots.

Implementation ideas

No response

[yada]

Thanks @pratik-mahalle, for the proposition, but I'm not sure it will be easy or feasible to list everything... especially based on how versatile Microcks deployment is (as you mentioned) but also based on the fact adopters are deploying Microcks on their infra and their own way... sometimes, we do not know how and the specifities they have intrioduced that they need to take about... my 2 cents. @lbroudoux, what are your thoughts on this proposition?

[lbroudoux]

As discussed with @pratik-mahalle on private Discord:

That's a good point, and I think this is because we just had once a breaking change during upgrade, and it was mentioned in the announcement blog post.
However, I admit that it can be surprising for first comers and we may add one dedicated page to track and to inform even if no specific action are required.

So +1 for adding such a page even if the content will be most of the time "just change the tag of the container image or run a Helm upgrade".

Regarding the location, I think that /documentation/guides/installation/upgrading.md can also be a good pick? What do you think?

[pratik-mahalle]

/onhold due to complexity