Describe the bug
Microcks currently lacks a dedicated, centralized guide for upgrading between versions. For users running Microcks in production, especially enterprise teams as this creates uncertainty during upgrades and increases reliance on release blogs or trial-and-error.
I’m proposing a new documentation page that serves as the single source of truth for upgrade and migration guidance.
📍 Proposed Location
/documentation/guides/administration/upgrading.md
This fits naturally alongside other admin-focused guides like users, secrets, and snapshots, where operators expect to find maintenance-related documentation.
Attach any resources that can help us understand the issue.
No response
Describe the bug
Microcks currently lacks a dedicated, centralized guide for upgrading between versions. For users running Microcks in production, especially enterprise teams as this creates uncertainty during upgrades and increases reliance on release blogs or trial-and-error.
I’m proposing a new documentation page that serves as the single source of truth for upgrade and migration guidance.
📍 Proposed Location
/documentation/guides/administration/upgrading.mdThis fits naturally alongside other admin-focused guides like users, secrets, and snapshots, where operators expect to find maintenance-related documentation.
Attach any resources that can help us understand the issue.
No response