Skip to content

Latest commit

 

History

History
137 lines (94 loc) · 2.16 KB

parameters.adoc

File metadata and controls

137 lines (94 loc) · 2.16 KB

Maxscale Parameters

The parent key for the following parameters is maxscale and they affect MaxScale itself:

namespace

type

string
default

syn-maxscale

The namespace in which to deploy this component.

master_only_listen_address

type

string
default

0.0.0.0

read_write_listen_address

type

string
default

0.0.0.0

db1_address

type

string
default

db1.mygalera.example.org

db1_port

type

string
default

3306

db2_address

type

string
default

db2.mygalera.example.org

db2_port

type

string
default

3306

db3_address

type

string
default

db3.mygalera.example.org

db3_port

type

string
default

3306

service_user

type

string
default

maxscale

monitor_user

type

string
default

maxscale

service_pwd

type

string
default

?{vaultkv:${customer:name}/${cluster:name}/maxscale/service_pwd}

monitor_pwd

type

string
default

?{vaultkv:${customer:name}/${cluster:name}/maxscale/monitor_pwd}

Container Resource Parameters

By default there are no resource limits. As soon as you set any of these reource parameters, all the other ones are set to their defaults and you’ll have to override them to change them. This prevents generating an invalid manifest.

resources.requests.cpu

type

string
default

1000m

resources.requests.memory

type

string
default

128Mi

resources.limits.cpu

type

string
default

2000m

resources.limits.memory

type

string
default

512Mi

Example

namespace: example-namespace
maxscale:
  db1_address: db5.othergalera.example.org
  db1_port: 3309
  db2_address: db6.othergalera.example.org
  db2_port: 3307
  db3_address: db7.othergalera.example.org
  db3_port: 3305
  monitor_user: mymonitoruser
  service_user: myserviceuser
  resources:
    requests:
      cpu: 1000m
      memory: 128Mi
    limits:
      cpu: 2000m
      memory: 512Mi