The Mattermost Operator currently defaults to a configuration that enables High Availability (HA) features (specifically replicas > 1) which are functionally unstable without an active Enterprise clustering license.
In the Community Edition, running multiple replicas leads to a fragmented state. This results in messages randomly failing to appear on clients until a manual refresh is performed.
Current Behavior: The Operator deploys multiple replicas by default. The system enters a "split-brain" state regarding real-time delivery.
Expected Behavior: The Operator should detect the absence of a license or default to replicas: 1 for community installations. High Availability should be an explicit opt-in feature, accompanied by a warning that it requires an Enterprise license to function correctly.
Proposed Mitigation/Fix:
-
Change Defaults: Set the default replica count to 1 in the Custom Resource Definition (CRD) or the Operator logic.
-
License Validation: If replicas > 1 is requested, the Operator should log a warning if no valid clustering license is detected.
-
Documentation: Explicitly state in the README/Documentation that multiple replicas are unsupported and unstable in the Community Edition.
The Mattermost Operator currently defaults to a configuration that enables High Availability (HA) features (specifically replicas > 1) which are functionally unstable without an active Enterprise clustering license.
In the Community Edition, running multiple replicas leads to a fragmented state. This results in messages randomly failing to appear on clients until a manual refresh is performed.
Current Behavior: The Operator deploys multiple replicas by default. The system enters a "split-brain" state regarding real-time delivery.
Expected Behavior: The Operator should detect the absence of a license or default to replicas: 1 for community installations. High Availability should be an explicit opt-in feature, accompanied by a warning that it requires an Enterprise license to function correctly.
Proposed Mitigation/Fix:
Change Defaults: Set the default replica count to 1 in the Custom Resource Definition (CRD) or the Operator logic.
License Validation: If replicas > 1 is requested, the Operator should log a warning if no valid clustering license is detected.
Documentation: Explicitly state in the README/Documentation that multiple replicas are unsupported and unstable in the Community Edition.