Increase grafana mem/cpu in mgmt cluster (!9491) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

We have seen a lot of sso tests that failed on grafana check (502 error), looking on the state of the pod I have noticed that in most of the cases the pods are in OOMKilled state.

containerStatuses:
  - allocatedResources:
      cpu: 100m
      memory: 100Mi
    containerID: containerd://4f9962f9e3d3fd497db4720e8c256d2e8be685d0ce0a2cbf402f7f80be5c23a6
    image: docker.io/rancher/appco-grafana:12.3.1-1.12
    imageID: docker.io/rancher/appco-grafana@sha256:c4508fe1195b873268c29d370dbff16fa366e5ef10582ad84c5ce0f4698bb49a
    lastState:
      terminated:
        containerID: containerd://7f3e887f43f6c6a07f31355e5ef585ab2de2f24933c6b25deb7267d1dfcf736d
        exitCode: 137
        finishedAt: "2026-10-08T15:19:49Z"
        reason: OOMKilled
        startedAt: "2026-10-08T15:03:41Z"
    name: grafana

https://gitlab.com/sylva-projects/sylva-core/-/jobs/17029889967

The aim of this MR is to increase the memory & cpu on grafana pod.

Related to #4767

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Oct 12, 2026 by Bogdan Antohe

Increase grafana mem/cpu in mgmt cluster

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports