Converting Mendix Operator from Namespace to Global Installation | Mendix Private Cloud Connected
0
I'm currently running a Mendix for Private Cloud setup using Namespace Installations of the Mendix Operator, where each operator manages a single namespace. I am exploring the possibility of moving to a Global Installation where a single operator manages multiple namespaces to streamline our infrastructure and reduce management overhead. My understanding from the Mendix documentation is that these are distinct setup choices made when initially registering the cluster, and I have not found a way to directly convert a Namespace Installation to a Global Installation. I am aware of the following key differences: • Namespace Installation: One operator per namespace. • Global Installation: A single operator managing multiple namespaces. • With a Global Operator, configurations in the managed namespace take precedence over the global namespace configuration. • Manual deletion of a namespace is required when using a Global Operator. • Private Cloud License Manager requires identical configurations in both global and managed namespaces. I'm looking for advice on the best approach for migrating from a Namespace Installation to a Global Installation. Specifically, I would like to know: • Is there a supported or recommended procedure for converting existing Namespace Installations to a Global Installation? • If a direct conversion isn't available, what are the recommended steps for manually migrating namespaces from a Namespace Installation to be managed by a new Global Installation? • What specific configuration changes are required to switch from a standard operator to a global operator, considering the different installation types? • What are the potential pitfalls or challenges I should be aware of when making this switch? • Are there any tools or scripts that can assist with this process, particularly when migrating multiple namespaces? • Are there any impacts on licensing when switching from Namespace to Global Installation, particularly related to the Private Cloud License Manager? I'm also interested in learning from the experiences of others who have attempted a similar migration. Any insights or best practices you can share would be greatly appreciated. Thank you for your time and expertise.