use fresh tags from sylva-elements repos after fork of release-1.7 (!8391) · Merge requests · Sylva-projects / sylva-core

The fork of release-1.7 is now in place.

In sylva-elements repo in which we maintain release branches, those branches have been created: assuming that x.y.z is the version used in sylva-core release-1.7 for a given sylva-elements sub-repo: * the release-x.y-sylva-1.7 branch has been created from tag x.y * the x.(y+1).0 was created on the same commit

To make it clear that on the main branch of those repos, x.(y+1). tags should now be used (or higher) and not x.y.*, and to let renovate know what to use in sylva-core main, this MR is making use of all those x.(y+1).0 tags here in sylva-core.

Those tags were created on the same commits as the tag they replace, so this MR should not actually change anything. Except hypothetical cases were the container rebuild done on the fresh tags would lead to different content -- that would be a pinning violation/bug.

Exceptions:

for kube-job image, the commit on which 1.6.1 had been done wasn't rebuildable without changes that landed after it to fix a gitlab.org runner MTU issue preventing some binaries download -- I did a v1.7.1 tag instead (diff between 1.7.0/1.6.1 and 1.7.1, which includes some binaries changes)

This MR was prepared following the hints provided by the new --check-tags-to-align option of tools/deps-project-tool.dev.py added in !8251 (merged).

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 Jul 01, 2026 by Thomas Morin

use fresh tags from sylva-elements repos after fork of release-1.7

CI configuration

Global config for deployment pipelines

Merge request reports