Restrict running less than 2 pods of proxySQL if unsafe flag is not set

Description

As a user, I expect that I cannot run less than 2 pods of proxySQL unless allowUnsafeConfigurations flag is set to true.

There will be series of tickets to ensure that allowUnsafeConfigurations flag is not only controlling safe configuration of database clusters, but all other components as well.

 

Also we are going to set default size for ProxySQL pods to 2, not 3.

Environment

None

Smart Checklist

Activity

Mykola Marzhan November 4, 2020 at 8:01 PM

, yes check is only about PXC right now.
maybe be we need to check proxysql/haproxy size also

Sergey Pronin November 4, 2020 at 8:08 AM

I managed to run proxysql and haproxy with size=1 even with allowUnsafeConfigurations = false. 

 is it expected behavior?

Mykola Marzhan October 14, 2020 at 11:04 AM

In other words I would say that we may allow running 1 proxy pod only if allowUnsafeConfigurations = true.

I think it has sense, I like this idea

Sergey Pronin October 12, 2020 at 12:54 PM
Edited

 one of the use cases for running 1 haproxy/proxysql pod is a dev environment (on minikube for example). What do you think?

 

In other words I would say that we may allow running 1 proxy pod only if allowUnsafeConfigurations = true.

Daniel Guzman Burgos June 22, 2020 at 5:38 PM

One should be enough for start (and by MS experience). More than one kinda waste node resources for PXC pods. 

We only uses more than one proxysql instance (normally, out of k8s context) for HA

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Smart Checklist

Created June 22, 2020 at 5:28 PM
Updated March 5, 2024 at 6:14 PM
Resolved August 9, 2021 at 8:08 AM

Flag notifications