Skip to content

Clarify Mendix on Kubernetes subscription requirement after Operator license removal#11615

Open
MXClyde wants to merge 3 commits into
mendix:developmentfrom
MXClyde:feature/clarify-operator-license-subscription
Open

Clarify Mendix on Kubernetes subscription requirement after Operator license removal#11615
MXClyde wants to merge 3 commits into
mendix:developmentfrom
MXClyde:feature/clarify-operator-license-subscription

Conversation

@MXClyde

@MXClyde MXClyde commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The Operator License alert on the Mendix on Kubernetes page implied a subscription was only needed for technical support, which caused real customer confusion after the standalone Operator license key was removed in Operator 2.23.0 (a customer asked support whether Mendix on Kubernetes still needed to be purchased at all).
  • Rewords the alert and the following paragraph to make clear that removing the license key was a technical change only, and a valid Mendix on Kubernetes subscription is still required to use the Operator, regardless of Operator version.
  • Also fixes a confusingly-ordered sentence in the Runtime License section that described the Runtime/Operator license relationship starting from the wrong subject.

Test plan

  • Rendered the page locally to confirm formatting/alert shortcodes are unaffected
  • Verified no other page content references the old wording

…ter Operator license removal

The Operator License alert implied a subscription was only needed for
technical support, which caused confusion for a customer and internally
after the standalone Operator license key was removed in Operator 2.23.0.
Makes explicit that removing the license key was a technical change only
and a valid subscription is still required to use the Operator.

Also fixes a sentence in the Runtime License section that described the
Runtime/Operator license relationship in a confusing order.
@katarzyna-koltun-mx katarzyna-koltun-mx self-assigned this Jul 27, 2026

@katarzyna-koltun-mx katarzyna-koltun-mx left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@MXClyde approved, should I merge directly?

@MXClyde

MXClyde commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

@MXClyde approved, should I merge directly?

Yes please!

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.

2 participants