Skip to content

Update Talos Linux v1.10.3 and fix assets - #1006

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

Update Talos Linux v1.10.3 and fix assets#1006
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
upd-talos

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented May 29, 2025

Copy link
Copy Markdown
Member

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

Summary by CodeRabbit

  • New Features

    • Installer artifacts now include an additional asset, improving the completeness of installation resources.
  • Bug Fixes

    • End-to-end tests and cluster setup now verify the presence of all required installer asset files, reducing setup errors.
  • Chores

    • Updated installer and system extension images to newer versions for improved stability and compatibility.
    • Improved build and test workflows to handle multiple installer assets and streamline artifact management.
    • Enhanced release workflows to validate version tags and automate asset downloads for testing.

@coderabbitai

coderabbitai Bot commented May 29, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

"""

Walkthrough

This change updates the handling of installer artifacts in CI workflows and tests. The GitHub Actions workflow now uploads both the installer YAML and a raw disk image as a single combined artifact. Test scripts and Makefile commands are adjusted to use these files directly, removing reliance on environment variables and external downloads. Several Talos installer profile YAMLs are updated to newer image versions.

Changes

File(s) Change Summary
.github/workflows/pull-requests.yaml Added build step for Talos nocloud image; consolidated artifact upload into one step with combined artifact; updated artifact download in test job.
.github/workflows/pull-requests-release.yaml Added steps to extract version tag from branch name; download release assets into local directory; simplified test step.
hack/e2e-cluster.bats, packages/core/testing/Makefile Tests now verify presence of two local asset files instead of env var; Makefile copies both assets into test container; removed env var usage.
packages/core/installer/images/talos/profiles/*.yaml Updated Talos installer profile YAMLs to newer base and system extension image versions/tags; removed some system extension references.
packages/core/installer/hack/gen-profiles.sh Expanded profile handling with case statement; fixed baseInstaller image version; removed some system extension references.
Makefile Removed trailing slash from directory path in make -C command for assets target.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Artifact Storage
    participant Test Runner

    GitHub Actions->Artifact Storage: Upload combined artifact "cozystack-artefacts" containing installer YAML and nocloud image
    Test Runner->Artifact Storage: Download "cozystack-artefacts" into _out/assets/
    Test Runner->Test Runner: Run tests using local asset files directly (kubectl apply from file)
Loading

Possibly related PRs

  • cozystack/cozystack#800: Related to release workflow branch name pattern handling and asset downloads.
  • cozystack/cozystack#1005: Also modifies CI workflow and test setup for installer artifacts, focusing on job splitting and artifact handling.
  • cozystack/cozystack#982: Introduces Bats-based end-to-end tests, including changes to the same test script updated here.

Suggested reviewers

  • lllamnyp
  • klinch0

Poem

🐇 In tunnels deep where code does play,
Two artifacts now lead the way.
No env vars to chase or find,
Just files on disk, well aligned.
Talos versions fresh and bright,
This bunny hops with pure delight!
🌿✨
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e41b618 and f798cbd.

📒 Files selected for processing (12)
  • .github/workflows/pull-requests-release.yaml (1 hunks)
  • .github/workflows/pull-requests.yaml (2 hunks)
  • Makefile (1 hunks)
  • hack/e2e-cluster.bats (3 hunks)
  • packages/core/installer/hack/gen-profiles.sh (2 hunks)
  • 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)
  • packages/core/testing/Makefile (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai 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.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf87779 and 22509bb.

📒 Files selected for processing (9)
  • .github/workflows/pull-requests.yaml (1 hunks)
  • hack/e2e-cluster.bats (2 hunks)
  • 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)
  • packages/core/testing/Makefile (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build
🔇 Additional comments (17)
packages/core/installer/images/talos/profiles/kernel.yaml (3)

6-6: Bump profile version to v1.10.3
Consistent upgrade from v1.10.1.


13-13: Update base installer imageRef to v1.10.3
Matches the new Talos release tag.


15-23: Refresh systemExtensions to v1.10.3 images and recent firmware dates
All referenced extensions (amd-ucode, bnx2-bnx2x, intel-ice-firmware, qlogic-firmware, drbd, zfs) align with the new release and date tags.

packages/core/installer/images/talos/profiles/metal.yaml (3)

6-6: Bump profile version to v1.10.3
Version increment is correct and consistent.


13-13: Update base installer imageRef to v1.10.3
Aligns with the updated Talos installer release.


15-23: Refresh systemExtensions to v1.10.3 images and recent firmware dates
Firmware and extension tags (amd-ucode, bnx2-bnx2x, intel-ice-firmware, qlogic-firmware, drbd, zfs) updated correctly.

.github/workflows/pull-requests.yaml (1)

44-47: Include raw disk image in artifact upload
The additional _out/assets/nocloud-amd64.raw.xz is now bundled under cozystack-installer, matching downstream test expectations.

packages/core/installer/images/talos/profiles/nocloud.yaml (3)

6-6: Bump profile version to v1.10.3
Upgraded from v1.10.1 as intended.


13-13: Update base installer imageRef to v1.10.3
Matches the new Talos version.


15-23: Refresh systemExtensions to v1.10.3 images and recent firmware dates
All extension tags (amd-ucode, bnx2-bnx2x, intel-ice-firmware, qlogic-firmware, drbd, zfs) are correctly bumped.

packages/core/installer/images/talos/profiles/initramfs.yaml (2)

6-6: Version update looks good.

The version bump from v1.10.1 to v1.10.3 is properly applied.


13-13: Base installer image reference updated correctly.

The base installer image has been updated to match the new version v1.10.3.

packages/core/installer/images/talos/profiles/installer.yaml (1)

6-23: Consistent version and system extension updates.

The updates in this installer profile are consistent with the initramfs profile, which is good for maintaining uniformity across all Talos profiles.

packages/core/installer/images/talos/profiles/iso.yaml (1)

6-23: Excellent consistency across all Talos profiles.

The iso profile updates maintain perfect consistency with the initramfs and installer profiles, ensuring uniform Talos v1.10.3 deployment across all output formats.

hack/e2e-cluster.bats (3)

6-16: Improved asset verification with explicit file checks.

The new approach of checking for specific installer asset files is more explicit and provides better error messaging than the previous environment variable check.


248-249: Better approach using direct file reference.

Applying the installer manifest directly from the file is more reliable than using an environment variable. This change aligns well with the artifact-based CI workflow updates.


7-13:

Details

✅ Verification successful

Verify file path consistency across the pipeline.

Ensure that the asset file paths _out/assets/cozystack-installer.yaml and _out/assets/nocloud-amd64.raw.xz are consistent with where these files are generated and placed by the CI workflow.


🏁 Script executed:

#!/bin/bash
# Verify that the expected asset paths are used consistently across the repository
echo "Checking for references to installer asset paths..."

# Search for cozystack-installer.yaml references
echo "=== cozystack-installer.yaml references ==="
rg "cozystack-installer\.yaml" --type yaml --type sh

# Search for nocloud-amd64.raw.xz references  
echo "=== nocloud-amd64.raw.xz references ==="
rg "nocloud-amd64\.raw\.xz" --type yaml --type sh

# Search for _out/assets/ path references
echo "=== _out/assets/ path references ==="
rg "_out/assets/" --type yaml --type sh

Length of output: 1532


Asset path consistency verified
I’ve confirmed that both hack/e2e-cluster.bats and hack/upload-assets.sh reference _out/assets/cozystack-installer.yaml and _out/assets/nocloud-amd64.raw.xz in the same location. No discrepancies were found—no changes needed here.

Comment thread packages/core/testing/Makefile Outdated
Comment on lines +15 to +21
- imageRef: ghcr.io/siderolabs/amd-ucode:20250509
- imageRef: ghcr.io/siderolabs/amdgpu-firmware:20241110
- imageRef: ghcr.io/siderolabs/bnx2-bnx2x:20250410
- imageRef: ghcr.io/siderolabs/bnx2-bnx2x:20250509
- imageRef: ghcr.io/siderolabs/i915-ucode:20241110
- imageRef: ghcr.io/siderolabs/intel-ice-firmware:20250410
- imageRef: ghcr.io/siderolabs/intel-ice-firmware:20250509
- imageRef: ghcr.io/siderolabs/intel-ucode:20250211
- imageRef: ghcr.io/siderolabs/qlogic-firmware:20250410
- imageRef: ghcr.io/siderolabs/drbd:9.2.13-v1.10.1
- imageRef: ghcr.io/siderolabs/zfs:2.3.1-v1.10.1
- imageRef: ghcr.io/siderolabs/qlogic-firmware:20250509
- imageRef: ghcr.io/siderolabs/drbd:9.2.13-v1.10.3
- imageRef: ghcr.io/siderolabs/zfs:2.3.2-v1.10.3

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.

💡 Verification agent

🧩 Analysis chain

Verify system extension image availability.

Multiple system extensions have been updated to newer versions. Please ensure these image references are valid and available.


🏁 Script executed:

#!/bin/bash
# Verify that the updated system extension images exist in the registry
images=(
  "ghcr.io/siderolabs/amd-ucode:20250509"
  "ghcr.io/siderolabs/bnx2-bnx2x:20250509" 
  "ghcr.io/siderolabs/intel-ice-firmware:20250509"
  "ghcr.io/siderolabs/qlogic-firmware:20250509"
  "ghcr.io/siderolabs/drbd:9.2.13-v1.10.3"
  "ghcr.io/siderolabs/zfs:2.3.2-v1.10.3"
)

for image in "${images[@]}"; do
  echo "Checking $image..."
  if ! docker manifest inspect "$image" >/dev/null 2>&1; then
    echo "ERROR: Image $image not found or not accessible"
    exit 1
  fi
done
echo "All system extension images are accessible"

Length of output: 645


Fix missing initramfs system extension image tags

The verification script indicates that at least one of the updated images is not found in the registry. Please confirm and correct the tags for all system extensions in packages/core/installer/images/talos/profiles/initramfs.yaml:

• Line 15: ghcr.io/siderolabs/amd-ucode:20250509 → image not found
• (Re-run verification for the remaining images once the above is fixed)

Action items:

  • Verify that each tag exists in the GHCR repository (docker manifest inspect …)
  • Update any invalid or unpublished tags to the correct, available versions
🤖 Prompt for AI Agents
In packages/core/installer/images/talos/profiles/initramfs.yaml around lines 15
to 23, some system extension image tags, such as
ghcr.io/siderolabs/amd-ucode:20250509, are not found in the registry. Verify the
existence of each image tag using docker manifest inspect or a similar command,
then update any invalid or unpublished tags to the correct, available versions
in the YAML file to ensure all image references are valid and accessible.

@kvaps
Andrei Kvapil (kvaps) force-pushed the upd-talos branch 2 times, most recently from 793ba64 to 0d35051 Compare May 29, 2025 18:15

@coderabbitai coderabbitai 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.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/core/installer/images/talos/profiles/nocloud.yaml (1)

13-13: Update baseInstaller image reference
The base installer has been switched to the new digest‐based registry and version.

There's a trailing space at the end of this line which will trigger a lint error.
Apply this diff to remove it:

-    imageRef: factory.talos.dev/nocloud-installer/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba:v1.10.3 
+    imageRef: factory.talos.dev/nocloud-installer/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba:v1.10.3
🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 13-13: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 793ba64 and 0d35051.

📒 Files selected for processing (10)
  • .github/workflows/pull-requests.yaml (2 hunks)
  • Makefile (1 hunks)
  • hack/e2e-cluster.bats (3 hunks)
  • 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)
  • packages/core/testing/Makefile (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/core/installer/images/talos/profiles/initramfs.yaml
  • packages/core/installer/images/talos/profiles/kernel.yaml
🚧 Files skipped from review as they are similar to previous changes (7)
  • .github/workflows/pull-requests.yaml
  • Makefile
  • packages/core/installer/images/talos/profiles/metal.yaml
  • packages/core/testing/Makefile
  • packages/core/installer/images/talos/profiles/iso.yaml
  • packages/core/installer/images/talos/profiles/installer.yaml
  • hack/e2e-cluster.bats
🧰 Additional context used
🪛 YAMLlint (1.37.1)
packages/core/installer/images/talos/profiles/nocloud.yaml

[error] 13-13: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build
🔇 Additional comments (7)
packages/core/installer/images/talos/profiles/nocloud.yaml (7)

6-6: Version bump to v1.10.3
The profile version has been correctly updated to v1.10.3, aligning with the rest of the Talos installers.


15-15: Update amd-ucode system extension
The firmware image for AMD microcode has been correctly bumped to the latest May 2025 build.


17-17: Update bnx2-bnx2x system extension
The Broadcom NIC firmware was updated to the May 2025 build as intended.


19-19: Update intel-ice-firmware system extension
Intel ICE firmware is now pinned to the May 2025 release, consistent with other extensions.


21-21: Update qlogic-firmware system extension
QLogic firmware has been updated to the latest build date as expected.


22-22: Update drbd system extension
DRBD version has been correctly aligned to 9.2.13 for Talos v1.10.3.


23-23: Update zfs system extension
ZFS has been bumped to 2.3.2 for compatibility with Talos v1.10.3.

@kvaps
Andrei Kvapil (kvaps) force-pushed the upd-talos branch 2 times, most recently from 80021ec to ba6aab3 Compare May 29, 2025 20:03

@coderabbitai coderabbitai 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.

Actionable comments posted: 0

♻️ Duplicate comments (2)
packages/core/installer/images/talos/profiles/initramfs.yaml (1)

15-21: Verify updated systemExtension image tags

Several system extension images have been bumped (e.g., amd-ucode:20250509, bnx2-bnx2x:20250509, intel-ice-firmware:20250509, etc.). Please ensure each new tag exists and is accessible in GHCR.

#!/bin/bash
# Verify initramfs system extension images in GHCR
images=(
  "ghcr.io/siderolabs/amd-ucode:20250509"
  "ghcr.io/siderolabs/bnx2-bnx2x:20250509"
  "ghcr.io/siderolabs/intel-ice-firmware:20250509"
  "ghcr.io/siderolabs/qlogic-firmware:20250509"
  "ghcr.io/siderolabs/drbd:9.2.13-v1.10.3"
  "ghcr.io/siderolabs/zfs:2.3.2-v1.10.3"
)

for img in "${images[@]}"; do
  echo "Checking $img..."
  if ! docker manifest inspect "$img" >/dev/null 2>&1; then
    echo "ERROR: $img not found or accessible"
    exit 1
  fi
done
echo "All initramfs system extension images are available"
packages/core/installer/images/talos/profiles/installer.yaml (1)

15-21: Verify updated systemExtension image tags

The system extension images were bumped here as well (e.g., amd-ucode:20250509, zfs:2.3.2-v1.10.3). Please re-run a verification to confirm each image tag is published and accessible.

#!/bin/bash
# Verify installer profile system extension images in GHCR
images=(
  "ghcr.io/siderolabs/amd-ucode:20250509"
  "ghcr.io/siderolabs/bnx2-bnx2x:20250509"
  "ghcr.io/siderolabs/intel-ice-firmware:20250509"
  "ghcr.io/siderolabs/qlogic-firmware:20250509"
  "ghcr.io/siderolabs/drbd:9.2.13-v1.10.3"
  "ghcr.io/siderolabs/zfs:2.3.2-v1.10.3"
)

for img in "${images[@]}"; do
  echo "Checking $img..."
  if ! docker manifest inspect "$img" >/dev/null 2>&1; then
    echo "ERROR: $img not found or accessible"
    exit 1
  fi
done
echo "All installer system extension images are available"
🧹 Nitpick comments (1)
packages/core/installer/hack/gen-profiles.sh (1)

79-79: Use dynamic TALOS_VERSION for baseInstaller

The baseInstaller.imageRef is hardcoded to v1.10.3, which will require manual updates on each bump. Consider leveraging the dynamically fetched $TALOS_VERSION instead:

-    imageRef: "ghcr.io/siderolabs/installer:v1.10.3"
+    imageRef: "ghcr.io/siderolabs/installer:${TALOS_VERSION}"

This change will automatically align the installer imageRef with the pulled Talos version.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d35051 and ba6aab3.

📒 Files selected for processing (11)
  • .github/workflows/pull-requests.yaml (2 hunks)
  • Makefile (1 hunks)
  • hack/e2e-cluster.bats (3 hunks)
  • packages/core/installer/hack/gen-profiles.sh (2 hunks)
  • 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)
  • packages/core/testing/Makefile (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (8)
  • Makefile
  • packages/core/installer/images/talos/profiles/metal.yaml
  • .github/workflows/pull-requests.yaml
  • packages/core/testing/Makefile
  • packages/core/installer/images/talos/profiles/iso.yaml
  • packages/core/installer/images/talos/profiles/kernel.yaml
  • hack/e2e-cluster.bats
  • packages/core/installer/images/talos/profiles/nocloud.yaml
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test
🔇 Additional comments (5)
packages/core/installer/images/talos/profiles/initramfs.yaml (2)

6-6: Confirm version bump consistency

The Talos profile version has been updated to v1.10.3, matching the PR objective and keeping it in sync with other profiles.


13-13: Approve baseInstaller image update

The baseInstaller.imageRef was correctly updated to
ghcr.io/siderolabs/installer:v1.10.3.
This aligns with the new Talos version.

packages/core/installer/images/talos/profiles/installer.yaml (2)

6-6: Confirm version bump consistency

The installer profile version has been updated to v1.10.3, in line with other Talos profiles.


13-13: Approve baseInstaller image update

The baseInstaller.imageRef now correctly references
ghcr.io/siderolabs/installer:v1.10.3.

packages/core/installer/hack/gen-profiles.sh (1)

35-64: Approve expanded profile handling

Refactoring the profile generation into a case statement for initramfs, kernel, iso, installer, metal, and nocloud enhances readability and simplifies future extensions.

@kvaps
Andrei Kvapil (kvaps) force-pushed the upd-talos branch 3 times, most recently from b21c2fe to e41b618 Compare May 29, 2025 20:38

@coderabbitai coderabbitai 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.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/pull-requests.yaml (1)

43-48: Remove trailing whitespace

Line 48 contains trailing spaces, triggering a YAML lint warning. Please remove the extra whitespace to keep the file clean and prevent lint errors.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 48-48: trailing spaces

(trailing-spaces)

.github/workflows/pull-requests-release.yaml (1)

62-64: Consider removing the file listing step

The ls -lh _out/assets/ is useful for debugging but may add noise in regular CI runs. You could optionally remove or gate this step behind a debug flag.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between be3f52f and e41b618.

📒 Files selected for processing (12)
  • .github/workflows/pull-requests-release.yaml (1 hunks)
  • .github/workflows/pull-requests.yaml (2 hunks)
  • Makefile (1 hunks)
  • hack/e2e-cluster.bats (3 hunks)
  • packages/core/installer/hack/gen-profiles.sh (2 hunks)
  • 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)
  • packages/core/testing/Makefile (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/core/installer/images/talos/profiles/installer.yaml
🚧 Files skipped from review as they are similar to previous changes (9)
  • Makefile
  • packages/core/testing/Makefile
  • packages/core/installer/images/talos/profiles/kernel.yaml
  • packages/core/installer/images/talos/profiles/iso.yaml
  • packages/core/installer/hack/gen-profiles.sh
  • packages/core/installer/images/talos/profiles/initramfs.yaml
  • packages/core/installer/images/talos/profiles/nocloud.yaml
  • hack/e2e-cluster.bats
  • packages/core/installer/images/talos/profiles/metal.yaml
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/pull-requests.yaml

[error] 48-48: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test
🔇 Additional comments (6)
.github/workflows/pull-requests.yaml (3)

40-42: Approve Talos image build step

The new step make -C packages/core/installer talos-nocloud correctly builds the Talos NoCloud image as part of the build job, aligning with the updated CI artifact flow.


49-53: Approve Talos image artifact upload

Uploading the Talos NoCloud image (talos-nocloud) as a separate artifact ensures downstream jobs can access the raw disk image directly alongside the installer YAML.


77-82: Approve Talos image download in test job

The test job now pulls down the talos-nocloud artifact into _out/assets/, matching the build output and removing external dependencies.

.github/workflows/pull-requests-release.yaml (3)

37-50: Approve tag extraction from PR branch

The actions/github-script block enforces the release-X.Y.Z[-suffix] naming convention and correctly outputs tag for downstream steps. This early validation helps catch misnamed release branches.


51-61: Approve download of required release assets

Using gh release download with explicit --pattern flags ensures that both cozystack-installer.yaml and nocloud-amd64.raw.xz are fetched into _out/assets/ before running tests.


66-66: Approve simplified test invocation

Switching from make manifests && make test to just make test matches the new asset-driven workflow and avoids unnecessary manifest generation in the release CI.

@kvaps
Andrei Kvapil (kvaps) force-pushed the upd-talos branch 2 times, most recently from 4ddb5c2 to 2e708e4 Compare May 29, 2025 21:01
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@kvaps Andrei Kvapil (kvaps) changed the title Update Talos Linux v1.10.3 Update Talos Linux v1.10.3 and fix assets. May 29, 2025
@kvaps Andrei Kvapil (kvaps) changed the title Update Talos Linux v1.10.3 and fix assets. Update Talos Linux v1.10.3 and fix assets May 29, 2025
@kvaps
Andrei Kvapil (kvaps) merged commit 9633ca4 into main May 29, 2025
@kvaps
Andrei Kvapil (kvaps) deleted the upd-talos branch May 29, 2025 21:27
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