Modify fluentd pods number and enable buffer persistency (!7291) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR changes the number of pods and enables the buffer persistence on fluentd.

Test coverage

I tested it on my dev environment and everything worked fine.

 k get po -n kube-logging | grep logging-fluentd
 logging-fluentd-0                           2/2     Running     0          20h
 logging-fluentd-1                           2/2     Running     0          17h
 logging-fluentd-configcheck-b9f5199a        0/1     Completed   0          20h

 kubectl get  -n kube-logging  pvc
 NAME                                       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      VOLUMEATTRIBUTESCLASS   AGE
 logging-fluentd-buffer-logging-fluentd-0   Bound    pvc-313d6e29-44ad-4083-94fe-1d88ff718b5a   5Gi       RWO            cinder-ceph-ssd   <unset>                 21h
 logging-fluentd-buffer-logging-fluentd-1   Bound    pvc-cb8a3dca-2d83-405b-92ed-08d874ca13e7   5Gi       RWO            cinder-ceph-ssd   <unset>                 19h

I also added pod AntiAffinity rules and set the StorageClass to the Default one.

kubectl get pod logging-fluentd-0 -n kube-logging -o jsonpath='{.spec.affinity.podAntiAffinity}'
{"requiredDuringSchedulingIgnoredDuringExecution":[{"labelSelector":
{"matchExpressions":[{"key":"app.kubernetes.io/component","operator":"In","values":["fluentd"]},
{"key":"app.kubernetes.io/name","operator":"In","values":["fluentd"]}]},
"topologyKey":"kubernetes.io/hostname"}]}

k get ks logging -o yaml
      5Gi\n                storageClassName: cinder-ceph-ssd\n

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 (i.e `real-bmh` for capm3 )

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 Jun 04, 2026 by Dragos Gerea

Modify fluentd pods number and enable buffer persistency

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports