As a software developer
I want a High Available Maxscale
So that I can deploy proxy clusters for services which are not prone to single point of failures.
Context
The current Maxscale helm chart appears to be a single node instance. If maxscale fails the connection to the proxy becomes single point of failure. There exist a maxscale topology for deploying a virtual IP along side 2 maxscale instances for automatic failover.
Out of Scope
N/A
Further links
Image of Virtual IP used Keepalived and 2 instances of Maxscale (Active and one standby) Topology
Acceptance criteria
Uses Virtual IP
Keepalived Config
Uses at least 2 maxscale instances where 1 is master and other(s) are the backup
Both maxscale.conf must be the same to serve as backup
Hi @advra ,
we're not actively using maxscale anymore and are therefore not planning to add more features to the chart. But we're happy to accept pull requests.
Summary
As a software developer I want a High Available Maxscale So that I can deploy proxy clusters for services which are not prone to single point of failures.
Context
The current Maxscale helm chart appears to be a single node instance. If maxscale fails the connection to the proxy becomes single point of failure. There exist a maxscale topology for deploying a virtual IP along side 2 maxscale instances for automatic failover.
Out of Scope
Further links
Image of Virtual IP used Keepalived and 2 instances of Maxscale (Active and one standby) Topology
Acceptance criteria