Skip to content

Conversation

@karlod-metalbear
Copy link
Contributor

Updated versioning documentation for clarity and consistency.

Updated versioning documentation for clarity and consistency.

This page describes how versioning and compatibility work across mirrord components.

### Component Compatibility
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can just be a H3 instead of H2 (same for rest)

Comment on lines +3 to +4
date: 2025-04-07T00:00:00.000Z
lastmod: 2025-04-07T00:00:00.000Z
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
date: 2025-04-07T00:00:00.000Z
lastmod: 2025-04-07T00:00:00.000Z
date: 2026-01-14T00:00:00.000Z
lastmod: 2026-01-14T00:00:00.000Z

Comment on lines +13 to +14
tags:
- enterprise
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not only relevant for enterprise customers, right?


# Versioning

mirrord is composed of multiple components, including the CLI, Operator, Agent, and License Server. These components may be deployed and upgraded independently, and mirrord is designed to support safe, incremental upgrades in production environments.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in production environments

This could be misunderstood. We never recommend using mirrord in production, so I'd use a different phrasing here.


### Component Compatibility

mirrord components communicate over well-defined APIs and do not require lockstep upgrades. In most cases, components can be upgraded independently as long as they remain within the same major version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

components can be upgraded independently as long as they remain within the same major version.

FYI, we have a different major for the charts. It's not it's own running component though, it's just a way to install the operator. So up to you, whatever you think would help users understand.

* Upgrade the mirrord Operator
* Upgrade client tooling (CLI) as needed

Upgrading the License Server first is safe because Operators are backward compatible with newer License Server versions within the same major version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operators are backward compatible with newer License Server versions

I'm not sure this part makes sense chronologically

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants