Set PriorityClass to system-cluster-critical for frr-k8s (!6976) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR sets priorityClassName: system-cluster-critical for metallb_helm_values in order to avoid pod eviction under node pressure.

Closes #3581 (closed)

Test coverage

This was tested on my environment by editing the values.yaml file and adding the metallb-l3 config as follows:

metallb:
  bgp_lbs: 
    l3_options:
      bfd_profiles:
        bfd-profile-bgp:
          receiveInterval: 1000
          transmitInterval: 1000
          detectMultiplier: 3

A daemonset was deployed that was containing the following field:

kubectl get daemonset.apps/metallb-frr-k8s -n metallb-system -o yaml  | grep -i "priorityclass"
priorityClassName: system-cluster-critical

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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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.

Set PriorityClass to system-cluster-critical for frr-k8s

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports