With stability tests, we see that mariadb gets OOM killed and has some
CPU throttling.
Putting higher limits in order to make it no happen.
Scaling also replicas from VFC and APPC db from 3 to 1.
Issue-ID: INT-1883
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I2699b34ac5fcaa805c6fc01592c5a5f607b17fae
disableNfsProvisioner: true
serviceAccount:
nameOverride: *appc-db
disableNfsProvisioner: true
serviceAccount:
nameOverride: *appc-db
dgbuilder:
nameOverride: appc-dgbuilder
dgbuilder:
nameOverride: appc-dgbuilder
resources:
small:
limits:
resources:
small:
limits:
- cpu: 500m
- memory: 2.5Gi
- cpu: 100m
- memory: 750Mi
+ cpu: 500m
+ memory: 2Gi
unlimited: {}
## MariaDB Galera containers' liveness and readiness probes
unlimited: {}
## MariaDB Galera containers' liveness and readiness probes
disableNfsProvisioner: true
serviceAccount:
nameOverride: *vfc-mariadb
disableNfsProvisioner: true
serviceAccount:
nameOverride: *vfc-mariadb
db: &dbConfig
mariadbService: vfc-mariadb
db: &dbConfig
mariadbService: vfc-mariadb
workflowPort: 10550
vfc-zte-vnfm-driver:
workflowPort: 10550
vfc-zte-vnfm-driver:
- enabled: true
\ No newline at end of file