Skip to content

Update Talos Linux v1.11.3 - #1527

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
upd-talos
Oct 16, 2025
Merged

Update Talos Linux v1.11.3#1527
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
upd-talos

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented Oct 16, 2025

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil kvapss@gmail.com

What this PR does

Release note

Update Talos Linux v1.11.3

Summary by CodeRabbit

  • Chores
    • Updated version to v1.11.3 across installer profiles.
    • Refreshed system extension images to latest available builds with updated firmware and driver versions.
    • Enhanced output format configuration for improved image generation.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello Andrei Kvapil (@kvaps), I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine maintenance update, upgrading the underlying Talos Linux operating system to its latest stable version, v1.11.3. This ensures that all deployment artifacts and system extensions are aligned with the most current and secure release of Talos Linux, providing improved stability and access to new features.

Highlights

  • Talos Linux Version Update: The core Talos Linux version has been updated from v1.10.6 to v1.11.3 across all relevant installer profiles.
  • System Extension Updates: All associated system extensions and the base installer image references have been updated to align with the new Talos Linux v1.11.3 release, including new SHA256 hashes for integrity.
  • lldpd Version Bump: The lldpd system extension has been updated from version 1.0.19 to 1.0.20.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment Gemini (@gemini-code-assist) Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Oct 16, 2025

Copy link
Copy Markdown
Contributor

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Six Talos installer profile YAML files are updated from version v1.10.6 to v1.11.3, with corresponding baseInstaller imageRef updates, systemExtensions list replacements featuring newer image tags (20250917 and v1.11.3 variants), and addition of output format specifications.

Changes

Cohort / File(s) Change Summary
Talos Profile Version & Image Updates
packages/core/installer/images/talos/profiles/initramfs.yaml, installer.yaml, iso.yaml, kernel.yaml, metal.yaml, nocloud.yaml
Version bumped from v1.10.6 to v1.11.3; baseInstaller.imageRef updated to v1.11.3; systemExtensions entries replaced with new imageRefs using 20250917/20250812 or v1.11.3 tags and updated SHA256 digests for amd-ucode, amdgpu, bnx2-bnx2x, intel-ice-firmware, i915, intel-ucode, qlogic-firmware, drbd, zfs, lldpd; output.outFormat added (raw or .xz depending on profile)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

The changes follow a consistent, repetitive pattern across all six profile files (version/imageRef bumps and systemExtensions list replacement), which reduces per-file review complexity. However, validation of new image digest values and tags against upstream Talos/Siderolabs releases is required to ensure correctness and compatibility.

Possibly related PRs

  • cozystack/cozystack#1351: Touches Talos profile systemExtensions and updates image references (lldpd and digest-pinned refs)
  • cozystack/cozystack#1006: Modifies the same Talos profile YAML files with baseInstaller.imageRef and systemExtensions updates

Suggested labels

release

Suggested reviewers

  • lllamnyp
  • klinch0

Poem

🐰 From v1.0 point six to one point one,
The profiles hop to newer spins,
Extensions swapped, digests all done,
Raw output formats—let the games begin!
With careful hops through YAML lands,
The Talos configs now expand. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed The title succinctly summarizes the primary change, which is the Talos Linux version bump to v1.11.3, and gives clear context without extraneous details.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch upd-talos

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates Talos Linux to version v1.11.3 and its associated system extension images across various profile configurations. The changes are consistent and correctly applied across all modified YAML files. My main feedback is regarding the significant code duplication in the configuration files. While these files are auto-generated, the duplication poses a maintainability challenge. I've added a specific comment with a suggestion to refactor the generation script to centralize the common configuration, which would make future updates easier and less error-prone.

Comment on lines +15 to +24
- imageRef: ghcr.io/siderolabs/amd-ucode:20250917@sha256:ff11ee9f1565d9f9b095a3dc41fb7962b211169b2ef05d658a488398cb98e2d2
- imageRef: ghcr.io/siderolabs/amdgpu:20250917-v1.11.3@sha256:527b694ddbc4b40e9529d736bfe9874cc786773aa5a1070bbefe77feb9a8a304
- imageRef: ghcr.io/siderolabs/bnx2-bnx2x:20250917@sha256:ac6aaaa0d3312e72279a5cde7de0d71fb61774aa2f97a4e56dd914a9f1dde4d1
- imageRef: ghcr.io/siderolabs/intel-ice-firmware:20250917@sha256:c25225c371e81485c64f339864ede410b560f07eb0fc2702a73315e977a6323d
- imageRef: ghcr.io/siderolabs/i915:20250917-v1.11.3@sha256:e8db985ff2ef702d5f3989b0138e1b9dd5ac5e885a3adefa5b42ee6fa32b7027
- imageRef: ghcr.io/siderolabs/intel-ucode:20250812@sha256:31142ac037235e6779eea9f638e6399080a1f09e7c323ffa30b37488004057a5
- imageRef: ghcr.io/siderolabs/qlogic-firmware:20250917@sha256:7094e5db6931a1b68240416b65ddc0f3b546bd9b8520e3cfb1ddebcbfc83e890
- imageRef: ghcr.io/siderolabs/drbd:9.2.14-v1.11.3@sha256:4393756875751e2664a04e96c1ccff84c99958ca819dd93b46b82ad8f3b4be67
- imageRef: ghcr.io/siderolabs/zfs:2.3.3-v1.11.3@sha256:3c0b34a760914980ac234e66f130d829e428018e46420b7bca33219b1cc2dd87
- imageRef: ghcr.io/siderolabs/lldpd:1.0.20@sha256:4c6370518f5b2e1f03214a6ed54778eaea663fda8850e3f4da174ed69b636172

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This list of system extensions is duplicated across all profile files (initramfs.yaml, installer.yaml, iso.yaml, kernel.yaml, metal.yaml, nocloud.yaml). While I understand these files are auto-generated (as noted by the comment at the top of the file), this duplication makes maintenance harder. For example, updating a single extension requires changes in many places, increasing the chance of errors.

Consider refactoring the generation script (packages/core/installer/hack/gen-profiles.sh) to avoid this duplication. One approach could be to use a common YAML file for shared configurations and merge it into each profile during generation. This would improve maintainability and reduce the potential for inconsistencies.

@kvaps
Andrei Kvapil (kvaps) merged commit 10516c3 into main Oct 16, 2025
21 checks passed
@kvaps
Andrei Kvapil (kvaps) deleted the upd-talos branch October 16, 2025 17:34
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.

2 participants