MariaDB provider adds MaxScale for read/write routing

The MariaDB provider v0.1.7 can put MariaDB MaxScale in front of galera and replication clusters. Switch on Enable MaxScale in the new Proxy section of the instance form, and MaxScale sends writes to the primary and balances reads across the other nodes. Applications keep a single endpoint: while the proxy is on, the connection Secret points at the MaxScale Service with the same credentials.

MaxScale only routes traffic. Primary failover and rejoin stay with the mariadb-operator. On the replication topology the provider turns off MaxScale’s own auto-failover, so the two never race for the primary (#37). You get two MaxScale replicas by default, and MaxScale terminates TLS when the engine requires it (tls.required: true).

MaxScale is licensed under the Business Source License, so check the terms before you enable it. Setup steps and an example are in the provider’s MaxScale proxy guide. Requires OpenEverest v2.0.0-dev.4 or later.