Skip to content

Add 3.7.0 release configuration - #108

Open
dprodanov4 wants to merge 5 commits into
suse-edge:mainfrom
dprodanov4:release-3.7.0
Open

Add 3.7.0 release configuration#108
dprodanov4 wants to merge 5 commits into
suse-edge:mainfrom
dprodanov4:release-3.7.0

Conversation

@dprodanov4

Copy link
Copy Markdown
Contributor

Moves the day2 fleets, bundles and scripts to Edge 3.7.0, matching the 3.7.0 release manifest in Factory.

  • Edge chart templates move to the 307 prefix (metal3 307.0.28+up0.15.1, metallb 307.0.3+up0.16.1, sriov + crd 307.1.0+up1.6.0, cdi/kubevirt 307.0.2+up0.7.0, kubevirt-dashboard 307.0.4+up1.3.3, endpoint-copier-operator 307.0.1+up0.3.0, turtles 307.0.7+up0.26.2)
  • OS upgrade plans and bundle go to 3.7.0; kubectl references switch to registry.suse.com/edge/3.7/kubectl:1.35.4
  • GitRepo revisions point at release-3.7.0
  • Longhorn temporarily sourced from upstream charts.longhorn.io at 1.12.0, since the Application Collection does not carry that version yet

k3s/rke2 plans and bundles already carry v1.35.4, so they are unchanged.

Verified against Factory release_manifest.yaml: no remaining 3.6/306. references, and chart versions match across Factory, stack-validation and fleet-examples.

Moves the day2 fleets, bundles and scripts to Edge 3.7.0. Edge chart
templates move to the 307 prefix, the OS upgrade plans and bundle go to
3.7.0, and kubectl references switch to registry.suse.com/edge/3.7.

GitRepo revisions now point at release-3.7.0 so the upgrade fleets are
sourced from this branch.
Rancher 2.15.x is only published on rancher-latest until Prime catches up
with the 3.7.0 baseline. NeuVector moves to the 110.x line that tracks
Rancher 2.15 and Elemental to 1.9.2.
Regenerates the Day 2 SUC plans, bundles and release artifact lists
from the 3.7.0 release manifest, moving RKE2 and K3s to v1.36.3 and
the kubectl image to 1.36.3.

The same regeneration picks up the kube-rbac-proxy 0.22.1 bump that
had already landed in Factory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant