Facilitate setting of rke2 default system registry (!6257) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Since we merged !5356 (merged) and sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster!831 (merged) we could benefit from rke2 system-default-registry option which has been fixed into latest RKE2 provider (see: https://github.com/rancher/cluster-api-provider-rke2/pull/739).

The aim of this MR is to facilitate the setting of rke2 default registry via s-c.

Closes #2980 (closed).

Test coverage

Tested locally:

apiVersion: controlplane.cluster.x-k8s.io/v1beta1
kind: RKE2ControlPlane
spec:
  agentConfig:
    additionalUserData:
      config: |
        {}
    cisProfile: cis
    format: cloud-config
    kubelet:
      extraArgs:
      - anonymous-auth=false
      - config=kubelet-configuration-file.yaml
      - eviction-hard=imagefs.available<5%,nodefs.available<5%,memory.available<1Gi
      - max-pods=210
      - node-status-max-images=200
      - provider-id=openstack:///{{ ds.meta_data.uuid }}
    ntp:
      enabled: false
      servers:
      - 172.20.4.108
    systemDefaultRegistry: foo.com

 cat /etc/rancher/rke2/config.yaml | grep -i "system"
system-default-registry: foo.com

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
🏗️	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.

Facilitate setting of rke2 default system registry

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports