[talos] Update Talos Linux v1.10.1 - #931
Conversation
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
WalkthroughThe changes update version numbers and image references across several Talos installer profile YAML files. Profile versions are incremented from v1.9.5 to v1.10.1, and system extension images are updated to newer versions, including drbd and zfs. No structural, format, or control flow modifications are introduced. Changes
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
packages/core/installer/images/talos/profiles/metal.yaml (1)
6-6: Profile version bumped to v1.10.1
This aligns with the Talos v1.10.1 release. Ensure thathack/gen-profiles.sh(the generator) is updated to emit this version automatically to avoid manual drift.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
packages/core/installer/images/talos/profiles/initramfs.yaml(1 hunks)packages/core/installer/images/talos/profiles/installer.yaml(1 hunks)packages/core/installer/images/talos/profiles/iso.yaml(1 hunks)packages/core/installer/images/talos/profiles/kernel.yaml(1 hunks)packages/core/installer/images/talos/profiles/metal.yaml(1 hunks)packages/core/installer/images/talos/profiles/nocloud.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Build and Test
🔇 Additional comments (13)
packages/core/installer/images/talos/profiles/metal.yaml (1)
15-23:Details
✅ Verification successful
Bumped all systemExtensions imageRefs
All firmware and component images have been updated to their correct date or version tags. Run a sweep to ensure no residualv1.9.5references remain in any profile.
🏁 Script executed:
#!/bin/bash # Check for any leftover v1.9.5 tags in Talos profiles rg -n "v1\\.9\\.5" packages/core/installer/images/talos/profilesLength of output: 64
No residual v1.9.5 tags found
Ranrg -n 'v1\.9\.5' packages/core/installer/images/talos/profiles—no matches detected. All systemExtensions imageRefs have been updated correctly.packages/core/installer/images/talos/profiles/iso.yaml (2)
6-6: Profile version bumped to v1.10.1
Matches the metal profile. Verifyhack/gen-profiles.shwas updated so future regenerations stay in sync.
15-23:Details
✅ Verification successful
SystemExtensions imageRef updates
Component versions are aligned with the new release. Ensure there are no stalev1.9.5tags left behind.
🏁 Script executed:
#!/bin/bash rg -n "v1\\.9\\.5" packages/core/installer/images/talos/profilesLength of output: 64
SystemExtensions imageRef updates verified
No lingeringv1.9.5tags found inpackages/core/installer/images/talos/profiles. Ready to merge.packages/core/installer/images/talos/profiles/nocloud.yaml (3)
6-6: Profile version bumped to v1.10.1
Consistent with other Talos profiles. Confirm generator updates so this remains durable.
15-23:Details
✅ Verification successful
Bumped systemExtensions imageRefs
All firmware and extension images are updated. Run a quick grep to catch any outdated references.
🏁 Script executed:
#!/bin/bash rg -n "v1\\.9\\.5" packages/core/installer/images/talos/profilesLength of output: 64
Bumped systemExtensions imageRefs – verified
No occurrences ofv1.9.5remain inpackages/core/installer/images/talos/profiles; all firmware and extension imageRefs are up to date.
13-13:Details
❓ Verification inconclusive
Updated baseInstaller imageRef to v1.10.1
Ensure this GHCR tag is valid and publicly pullable.
🏁 Script executed:
#!/bin/bash # Verify the image tag on GHCR gh api /repos/siderolabs/installer/releases/tags/v1.10.1 --jq .tag_nameLength of output: 231
🏁 Script executed:
#!/bin/bash # Verify GHCR image tag v1.10.1 via registry manifest check set -e http_status=$(curl -s -o /dev/null -w "%{http_code}" \ -H "Accept: application/vnd.oci.image.manifest.v1+json" \ https://ghcr.io/v2/siderolabs/installer/manifests/v1.10.1) echo "HTTP status code for manifest v1.10.1: $http_status"Length of output: 277
Public GHCR Image Pullability Check Needed
The registry manifest check forghcr.io/siderolabs/installer:v1.10.1returned HTTP 401, indicating it may not be publicly accessible. Please verify that this tag exists and is set to public-read. You can test with:
docker pull ghcr.io/siderolabs/installer:v1.10.1File:
packages/core/installer/images/talos/profiles/nocloud.yaml(line 13)packages/core/installer/images/talos/profiles/installer.yaml (3)
6-6: Profile version bumped to v1.10.1
Aligned with all installer profiles. Don’t forget to bump the generator source.
15-23:Details
✅ Verification successful
SystemExtensions imageRef updates
All extensions version-locked to the new release. Verify no legacyv1.9.5remains.
🏁 Script executed:
#!/bin/bash rg -n "v1\\.9\\.5" packages/core/installer/images/talos/profilesLength of output: 64
SystemExtensions imageRef updates verified
No legacyv1.9.5references found inpackages/core/installer/images/talos/profiles.
Approving these changes.
13-13:Details
❓ Verification inconclusive
Updated baseInstaller imageRef to v1.10.1
Check that the tag exists before merging to prevent downstream failures.
🏁 Script executed:
#!/bin/bash curl -sSL -I https://ghcr.io/v2/siderolabs/installer/manifests/v1.10.1 | head -n 1Length of output: 96
Confirm GHCR tag exists with authentication
The initialcurlcheck returned HTTP/2 401 due to missing credentials. Please authenticate and verify thatv1.10.1is published before merging to avoid downstream failures.• Location:
packages/core/installer/images/talos/profiles/installer.yamlline 13Suggested verification steps:
# Authenticate to GHCR using a PAT echo "$GHCR_PAT" | docker login ghcr.io -u "$GHCR_USERNAME" --password-stdin # Confirm the manifest exists docker manifest inspect ghcr.io/siderolabs/installer:v1.10.1 > /dev/nullOr, if you prefer curl:
curl -I \ -H "Authorization: Bearer $GHCR_PAT" \ -H "Accept: application/vnd.oci.image.manifest.v1+json" \ https://ghcr.io/v2/siderolabs/installer/manifests/v1.10.1packages/core/installer/images/talos/profiles/kernel.yaml (2)
6-6: Profile version bumped to v1.10.1
Kernel profile updated in tandem. Make sure regeneration script uses v1.10.1.
15-23:Details
✅ Verification successful
SystemExtensions imageRef updates
Firmware/component images are all in sync with v1.10.1. Grep for any stray v1.9.5 strings to ensure completeness.
🏁 Script executed:
#!/bin/bash rg -n "v1\\.9\\.5" packages/core/installer/images/talos/profilesLength of output: 64
SystemExtensions imageRef updates verified
Firmware/component images in
packages/core/installer/images/talos/profiles/kernel.yamlare all updated to v1.10.1, and no strayv1.9.5references remain.packages/core/installer/images/talos/profiles/initramfs.yaml (2)
6-6: Bump profile version and base installer image to v1.10.1The
versionandbaseInstaller.imageRefhave been updated to v1.10.1, matching the PR objective and other installer profiles.Also applies to: 13-13
15-15: Update system extension image references to new date and component versionsAll listed system extensions have been bumped to the April 2025 date tags or v1.10.1 component versions (notably drbd and zfs), consistent with the broader Talos v1.10.1 updates.
Also applies to: 17-17, 19-19, 21-23
| path: /usr/install/amd64/initramfs.xz | ||
| baseInstaller: | ||
| imageRef: ghcr.io/siderolabs/installer:v1.9.5 | ||
| imageRef: ghcr.io/siderolabs/installer:v1.10.1 |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Updated baseInstaller imageRef to v1.10.1
Consistent with the new profile version. Confirm the GHCR tag exists and is publicly accessible to prevent CI failures.
🏁 Script executed:
#!/bin/bash
# Verify the installer image tag is available on GHCR
gh api /repos/siderolabs/installer/releases/tags/v1.10.1 --jq .tag_nameLength of output: 231
Updated baseInstaller imageRef to v1.10.1
Consistent with the new profile version. Confirm the GHCR container image tag exists and is publicly accessible to prevent CI failures.
File: packages/core/installer/images/talos/profiles/metal.yaml
Lines: 13
imageRef: ghcr.io/siderolabs/installer:v1.10.1Suggested verification (check for HTTP 200 OK):
#!/bin/bash
# Verify GHCR container image tag
curl -sI \
-H "Accept: application/vnd.docker.distribution.manifest.v2+json" \
https://ghcr.io/v2/siderolabs/installer/manifests/v1.10.1 \
| head -n 1Or using Docker:
docker manifest inspect ghcr.io/siderolabs/installer:v1.10.1| path: /usr/install/amd64/initramfs.xz | ||
| baseInstaller: | ||
| imageRef: ghcr.io/siderolabs/installer:v1.9.5 | ||
| imageRef: ghcr.io/siderolabs/installer:v1.10.1 |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Updated baseInstaller imageRef to v1.10.1
Double-check the GHCR manifest for this tag to avoid cyclic CI failures.
🏁 Script executed:
#!/bin/bash
# Confirm GHCR installer image exists
curl -sSL -I https://ghcr.io/v2/siderolabs/installer/manifests/v1.10.1 | head -n 1Length of output: 96
Verify image tag via pull, not curl manifest
GHCR’s registry API requires auth, so a curl Manifest check returns HTTP/2 401 even if the tag exists. To avoid CI failures, confirm the image is pullable:
# Confirm GHCR installer image exists by pulling it
docker pull ghcr.io/siderolabs/installer:v1.10.1Alternatively, you can use the GitHub CLI to inspect the manifest with proper headers:
gh api \
-H "Accept: application/vnd.oci.image.manifest.v1+json" \
/v2/siderolabs/installer/manifests/v1.10.1 \
--hostname ghcr.io- File:
packages/core/installer/images/talos/profiles/iso.yaml(line 13) - Ensure the pull succeeds in your environment or CI before merging.
| path: /usr/install/amd64/initramfs.xz | ||
| baseInstaller: | ||
| imageRef: ghcr.io/siderolabs/installer:v1.9.5 | ||
| imageRef: ghcr.io/siderolabs/installer:v1.10.1 |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Updated baseInstaller imageRef to v1.10.1
Validate the GHCR release tag prior to merge.
🏁 Script executed:
#!/bin/bash
gh api /repos/siderolabs/installer/releases/tags/v1.10.1 --jq .tag_nameLength of output: 231
Invalid GHCR imageRef: v1.10.1 tag not found
The GitHub release tag v1.10.1 does not exist in the siderolabs/installer repository (API returned 404). Please verify the correct tag or publish the release before merging.
• File: packages/core/installer/images/talos/profiles/kernel.yaml
Line 13:
- imageRef: ghcr.io/siderolabs/installer:v1.10.1
+ imageRef: ghcr.io/siderolabs/installer:<correct-tag>Committable suggestion skipped: line range outside the PR's diff.
Signed-off-by: Andrei Kvapil <kvapss@gmail.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated installer and system component versions to v1.10.1 across all profiles. - Refreshed system extension images to newer releases, including updated versions for drbd and zfs. - Applied recent date-based updates to firmware and extension images for improved support and compatibility. <!-- end of auto-generated comment: release notes by coderabbit.ai --> (cherry picked from commit a240c0b) Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>
Signed-off-by: Andrei Kvapil kvapss@gmail.com
Summary by CodeRabbit