Migrate from ingress-nginx to traefik (!8872) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR introduces Traefik as the default ingress controller and handles the migration of existing clusters automatically at upgrade time.

For consistency, the nginx IngressClass was kept. Traefik's compatibility provider matches Ingresses on the spec.controller of the IngressClass they reference rather than on its name, so the traefik unit re-creates an IngressClass named nginx bound to the rke2.cattle.io/ingress-nginx-migration controller, and Traefik picks the existing Ingresses up unchanged. That object is only rendered outside the coexistence phase, precisely so it does not collide with the nginx class that ingress-nginx still owns while both controllers are running.

How the migration runs

Two new _internal.state variables drive it. ingress_nginx_is_deployed looks up the ingress-nginx HelmRelease, and traefik_deploy_completed reads the enabled-units data of the sylva-units-status ConfigMap to tell whether a reconciliation with Traefik enabled has already gone all the way through. Their combination yields a coexistence phase and a cutover phase, and additional_reconciliation_requested.ingress_migration_in_progress makes sylva-units schedule the follow-up reconciliation.

In the coexistence reconciliation, ingress-nginx keeps serving ports 80 and 443 of the external IP untouched while Traefik is deployed alongside it on 8000 and 8443. The nginx class still belongs to ingress-nginx here, so Traefik serves nothing yet and there is no race condition happening.

In the cutover reconciliation, the ingress-nginx unit is disabled through its new enabled_conditions, but its Kustomization now carries prune: false, so Flux does not tear it down. Instead, ingress-nginx-cleanup deletes its HelmRelease at an explicit point in the dependency graph, immediately before the traefik unit reconciles onto ports 80/443 and recreates the nginx class pointing at itself.

The Helm unit tests were created by Claude Opus 5.

Closes #3329 (closed)

This MR makes use of sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster!1099 (merged)

Slides presented during Sylva weekly meeting that explain how the transition is implemented: traefik_migration_deck.pdf

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 Sep 16, 2026 by Thomas Morin

Migrate from ingress-nginx to traefik

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports