suse-edge/Factory
SHA256
17
0
Fork 18
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

rancher-turtles: updates to align with 0.19.0 #150

Merged
steven.hardy merged 1 commits from steven.hardy/Factory:turtles_019 into main 2025-07-10 10:11:34 +02:00
Conversation 2 Commits 1 Files Changed 6 +478 -20
steven.hardy commented 2025-05-09 16:47:25 +02:00
Owner
Copy Link

Updates derived from https://github.com/suse-edge/charts/pull/209

Updates derived from https://github.com/suse-edge/charts/pull/209
steven.hardy added 1 commit 2025-05-09 16:47:26 +02:00
rancher-turtles-airgap-resources: Updates for 0.19.0 fe8d0ba120
steven.hardy requested review from dprodanov 2025-05-09 16:47:42 +02:00
steven.hardy requested review from nbelouin 2025-05-09 16:47:42 +02:00
steven.hardy requested review from kzhelyazkov 2025-05-09 16:47:49 +02:00
steven.hardy requested review from fdegirmenci 2025-05-09 16:47:56 +02:00
dprodanov reviewed 2025-05-09 17:51:44 +02:00
rancher-turtles-chart/values.yaml Outdated
@@ -11,2 +23,3 @@
rancherInstalled: false
kubectlImage: "%%IMG_REPO%%/%%IMG_PREFIX%%kubectl:1.30.3"
# kubectlImage: Image for kubectl tasks.
kubectlImage: registry.suse.com/edge/3.2/kubectl:1.30.3
dprodanov commented 2025-05-09 17:50:37 +02:00
Owner
Copy Link

should we revert this to the old way? With %%IMG_REPO%%/%%IMG_PREFIX%%. The build is currently failing because of this registry not being authorized.
Error: registry.suse.com/edge/3.2/kubectl:1.30.3 is not from authorized source

should we revert this to the old way? With `%%IMG_REPO%%/%%IMG_PREFIX%%`. The build is currently failing because of this registry not being authorized. `Error: registry.suse.com/edge/3.2/kubectl:1.30.3 is not from authorized source `
steven.hardy commented 2025-05-09 19:20:16 +02:00
Author
Owner
Copy Link

Ah good catch, thanks - will do.

We should probably also build a newer kubectl image to avoid violating the version skew policy with 1.32 but perhaps that can be done as a followup as I think we also need to update other places after building a newer image

Ah good catch, thanks - will do. We should probably also build a newer kubectl image to avoid violating the [version skew policy](https://kubernetes.io/releases/version-skew-policy/#kubectl) with 1.32 but perhaps that can be done as a followup as I think we also need to update other places after building a newer image
dprodanov marked this conversation as resolved
steven.hardy force-pushed turtles_019 from af1f5b7a14 to 3a654b9826 2025-05-09 19:25:59 +02:00 Compare
dprodanov approved these changes 2025-05-12 18:53:48 +02:00
steven.hardy merged commit 3a654b9826 into main 2025-05-13 10:04:20 +02:00
steven.hardy deleted branch turtles_019 2025-05-13 10:04:20 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
nbelouin
kzhelyazkov
fdegirmenci
dprodanov
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
amorgante antaloala atanasdinov atrendafilov dbekhit dprodanov eminguez fdegirmenci geoagriogiannis ipetrov117 jarndt jtomasek kzhelyazkov mchiappero mkrutov nbelouin roxenham steven.hardy
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: suse-edge/Factory#150
Delete Branch "steven.hardy/Factory:turtles_019"

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?