suse-edge/Factory
SHA256
14
0
Fork 15
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update versions for 3.3 #131

Merged
steven.hardy merged 1 commits from steven.hardy/Factory:3.3_versions into main 2025-05-06 17:23:23 +02:00
Conversation 5 Commits 1 Files Changed 1 +15 -15
steven.hardy commented 2025-04-25 17:12:54 +02:00
Owner
Copy Link

Rancher prime 2.11.1 was released, so align with that and also the related
RKE2/k3s version and updated Longhorn/Neuvector charts

Rancher prime 2.11.1 was released, so align with that and also the related RKE2/k3s version and updated Longhorn/Neuvector charts
steven.hardy requested review from dprodanov 2025-04-25 17:12:55 +02:00
steven.hardy requested review from fdegirmenci 2025-04-25 17:12:55 +02:00
steven.hardy requested review from ipetrov117 2025-04-25 17:12:55 +02:00
fdegirmenci requested review from amorgante 2025-04-28 09:38:33 +02:00
fdegirmenci requested review from kzhelyazkov 2025-04-28 09:38:34 +02:00
fdegirmenci commented 2025-04-28 09:39:31 +02:00
Owner
Copy Link

Thanks for the PR @steven.hardy. I have a few things to note.

i wanted to send a commit to do the version updates but i wasn't allowed so

  • can you please bump metal3 chart to 999.0.2+up0.11.0 as this is what we have in SV so we keep release manifest and SV in sync?
  • i tested elemental 1.6.8 in SV with the versions you included in this PR and it works. can we bump elemental and elemental-operator-crds to 1.6.8?

additionally and more importantly, rke2 1.32.3 contains ingress-nginx cve fix however doing this will break 3.3 telco work as the kernel-rt version used there doesn't contain the kernel fix. added @kzhelyazkov and @amorgante so they can keep an eye on this PR. as you will see, I started a thread about this issue on Slack to decide the way forward.

Thanks for the PR @steven.hardy. I have a few things to note. i wanted to send a commit to do the version updates but i wasn't allowed so * can you please bump metal3 chart to `999.0.2+up0.11.0` as this is what we have in SV so we keep release manifest and SV in sync? * i tested elemental `1.6.8` in SV with the versions you included in this PR and it works. can we bump elemental and elemental-operator-crds to `1.6.8`? additionally and more importantly, rke2 1.32.3 contains ingress-nginx cve fix however doing this will break 3.3 telco work as the kernel-rt version used there doesn't contain the kernel fix. added @kzhelyazkov and @amorgante so they can keep an eye on this PR. as you will see, I started a thread about this issue on Slack to decide the way forward.
steven.hardy commented 2025-04-28 10:58:19 +02:00
Author
Owner
Copy Link

additionally and more importantly, rke2 1.32.3 contains ingress-nginx cve fix however doing this will break 3.3 telco work as the kernel-rt version used there doesn't contain the kernel fix. added @kzhelyazkov and @amorgante so they can keep an eye on this PR. as you will see, I started a thread about this issue on Slack to decide the way forward.

I think we have two options, either we hold this PR until the kernel-rt fix is released, or I can temporarily revert to 1.32.2 then we can do the k8s bump as a follow-up?

> additionally and more importantly, rke2 1.32.3 contains ingress-nginx cve fix however doing this will break 3.3 telco work as the kernel-rt version used there doesn't contain the kernel fix. added @kzhelyazkov and @amorgante so they can keep an eye on this PR. as you will see, I started a thread about this issue on Slack to decide the way forward. I think we have two options, either we hold this PR until the kernel-rt fix is released, or I can temporarily revert to 1.32.2 then we can do the k8s bump as a follow-up?
fdegirmenci commented 2025-04-28 11:00:12 +02:00
Owner
Copy Link

I think we have two options, either we hold this PR until the kernel-rt fix is released, or I can temporarily revert to 1.32.2 then we can do the k8s bump as a follow-up?

i think we can revert rke2 to 1.32.2 and merge the PR so we test all the updates except rke2 and we have only 1 thing to keep track of.

> I think we have two options, either we hold this PR until the kernel-rt fix is released, or I can temporarily revert to 1.32.2 then we can do the k8s bump as a follow-up? i think we can revert rke2 to `1.32.2` and merge the PR so we test all the updates except rke2 and we have only 1 thing to keep track of.
steven.hardy force-pushed 3.3_versions from d98ac61895 to 27dbdd5ad3 2025-04-28 15:53:54 +02:00 Compare
fdegirmenci approved these changes 2025-04-28 16:06:56 +02:00
Dismissed
steven.hardy force-pushed 3.3_versions from 27dbdd5ad3 to 229cf46fd2 2025-05-02 12:29:14 +02:00 Compare
fdegirmenci approved these changes 2025-05-02 14:19:38 +02:00
steven.hardy force-pushed 3.3_versions from 229cf46fd2 to 2c4991cb24 2025-05-06 16:34:51 +02:00 Compare
steven.hardy merged commit 2c4991cb24 into main 2025-05-06 17:23:23 +02:00
steven.hardy deleted branch 3.3_versions 2025-05-06 17:23:23 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
ipetrov117
dprodanov
amorgante
kzhelyazkov
fdegirmenci
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
amorgante atanasdinov atrendafilov dbekhit dprodanov eminguez fdegirmenci geoagriogiannis ipetrov117 jtomasek kzhelyazkov mchiappero nbelouin roxenham steven.hardy
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: suse-edge/Factory#131
No description provided.
Delete Branch "steven.hardy/Factory:3.3_versions"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?