[backport-1.6] Enable monitoring and Grafana BGP dashboard for MetalLB frr-k8s mode (!7888) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

kube-rbac-proxy version bump (v0.16.0 → v0.18.1)

In release-1.6, frr-k8s was using kube-rbac-proxy at tag v0.16.0, while main uses v0.18.1.

Containers kube-rbac-proxy and kube-rbac-proxy-frr from frr-k8s pods, running quay.io/brancz/kube-rbac-proxy image in v0.16.0, are not binding 9140/9141 ports (used to proxy metrics from internal containers to Prometheus, via kube-rbac-proxy).

This caused BGP peers to not be visible in Grafana dashboards when using the release-1.6 branch.

Bumping kube-rbac-proxy to v0.18.1 fixes the BGP metrics collection, making BGP peers visible again in Grafana on both management and workload clusters.

This version bump is an exception to the usual policy of not bumping versions in release branches, justified by the functional regression it fixes.

Closes #3897 (closed)

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 May 21, 2026 by Andra-Simona Delicostea

[backport-1.6] Enable monitoring and Grafana BGP dashboard for MetalLB frr-k8s mode

What does this MR do and why?

kube-rbac-proxy version bump (v0.16.0 → v0.18.1)

CI configuration

Global config for deployment pipelines

Merge request reports