Add support for aarch64 platform

[NickCao]

Summary by CodeRabbit

• Tests

  • Enhanced the testing process to run end-to-end tests concurrently on multiple operating system configurations for improved validation.

• Chores

  • Refined the deployment process by updating the container solution and command procedures for secret management, ensuring optimal compatibility.

[coderabbitai]

Walkthrough

This pull request introduces two key modifications. The GitHub Actions workflow for end-to-end testing is updated to use a matrix strategy, allowing tests to run concurrently on both ubuntu-24.04 and ubuntu-24.04-arm environments. Additionally, the helm chart for the jumpstarter controller updates the secrets job by switching the container image and replacing OpenShift CLI commands with their Kubernetes counterparts.

Changes

File(s)	Summary
.github/workflows/e2e.yaml	Replaced fixed OS (ubuntu-latest) with a matrix strategy using ubuntu-24.04 and ubuntu-24.04-arm for parallel e2e testing runs.
deploy/helm/jumpstarter/.../secrets-job.yaml	Updated container image to quay.io/jumpstarter-dev/jumpstarter-utils:latest and replaced oc commands with kubectl commands for secret operations.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant R1 as Runner (Ubuntu-24.04)
    participant R2 as Runner (Ubuntu-24.04-arm)

    Dev->>GH: Push commit
    GH->>R1: Trigger e2e-tests on Ubuntu-24.04
    GH->>R2: Trigger e2e-tests on Ubuntu-24.04-arm
    R1-->>GH: Report test results
    R2-->>GH: Report test results

Loading

Possibly related PRs

• Fix e2e test #78: Involves similar updates in the GitHub Actions workflow affecting end-to-end testing configurations.

Suggested reviewers

• mangelajo

Poem

I'm a hopping rabbit, coding with delight,
Changing workflows to run tests both day and night.
Parallel paths on Ubuntu shine so bright,
Secrets now dance with kubectl in flight.
With every commit, the code grows ever so right! 🐰

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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]

Actionable comments posted: 0

🧹 Nitpick comments (2)

deploy/helm/jumpstarter/charts/jumpstarter-controller/templates/secrets-job.yaml (1)

25-26: Consistency in Namespace Flag Format

The commands now use kubectl for secret management—which is great—but there is an inconsistency in how the namespace flag is specified. Line 25 uses:

-n {{ $namespace }}

while line 26 uses:

-n={{ $namespace }}

Standardizing to a single format (for example, -n {{ $namespace }}) might prevent potential parsing issues.

.github/workflows/e2e.yaml (1)

22-27: Clarify the Need for Duplicate e2e Test Job

There are two e2e test jobs defined: one using the new matrix strategy and another using a fixed ubuntu-latest runner. If both jobs serve distinct purposes or are intended to cover separate scenarios, please consider adding comments to clarify the rationale. Otherwise, you might consolidate these jobs for easier maintenance.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cc2fa19 and 28ea7df.

📒 Files selected for processing (2)

• .github/workflows/e2e.yaml (1 hunks)
• deploy/helm/jumpstarter/charts/jumpstarter-controller/templates/secrets-job.yaml (1 hunks)

🧰 Additional context used

🪛 actionlint (1.7.4)

.github/workflows/e2e.yaml

14-14: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: e2e-tests (ubuntu-24.04)
• GitHub Check: e2e-tests (ubuntu-24.04-arm)
• GitHub Check: e2e-tests-28d6b1cc3b49ab9ae176918ab9709a2e2522c97e

🔇 Additional comments (2)

deploy/helm/jumpstarter/charts/jumpstarter-controller/templates/secrets-job.yaml (1)

18-18: Container Image Update Verified

The container image has been updated to quay.io/jumpstarter-dev/jumpstarter-utils:latest, which aligns with the migration away from OpenShift CLI. Please ensure that this new image is validated in your deployment tests on all supported platforms.

.github/workflows/e2e.yaml (1)

10-15:

❓ Verification inconclusive

Matrix Strategy with Potential Runner Label Issue

The new matrix strategy for the e2e-tests job (covering both ubuntu-24.04 and ubuntu-24.04-arm) is a solid approach for enabling concurrent testing, which supports the aarch64 platform objective. However, static analysis indicates that the label ubuntu-24.04-arm may not be recognized by available runner configurations. Verify that your self-hosted or cloud runner setup accepts this custom label. If not, consider switching to a supported label (such as arm or arm64) to ensure tests run correctly.

---

Below is a shell script that searches the repository for any occurrences of "ubuntu-24.04-arm". Running this can help verify if the custom runner label is defined or referenced elsewhere (for example, in custom self-hosted runner configurations). If the search turns up no additional configuration that explicitly supports "ubuntu-24.04-arm", you may need to update the label to one that is recognized (e.g., "arm" or "arm64").

Once you review the output of this script:

• If you find that your infrastructure explicitly defines or supports "ubuntu-24.04-arm", you can safely ignore this concern.
• Otherwise, consider updating the label to one supported by your runner configuration.

Verify Custom Runner Label in GitHub Actions Workflow

---

🏁 Script executed:

#!/bin/bash
# Search the entire repository for occurrences of the custom runner label "ubuntu-24.04-arm"
rg "ubuntu-24.04-arm" -n .

Length of output: 148

---

Below is a new shell script to narrow the search specifically within the workflow file to confirm the occurrence of the custom runner label:

Based on prior results and the absence of additional configuration references in the repository, it appears that “ubuntu-24.04-arm” is only mentioned in the workflow file. Please manually verify that your self-hosted or cloud runner setup supports this custom label. If your runner configuration does not recognize it, consider switching to a supported label (such as arm or arm64) so that the tests can run correctly.

Action:

• Confirm the runner configuration supports the custom label ubuntu-24.04-arm.
• If not, update the workflow to use a recognized label (e.g., arm or arm64).

---

🏁 Script executed:

#!/bin/bash
# Check for "ubuntu-24.04-arm" specifically within the e2e workflow file
grep -n "ubuntu-24.04-arm" .github/workflows/e2e.yaml || echo "Custom label not found in .github/workflows/e2e.yaml"

Length of output: 207

---

Matrix Strategy: Confirm Custom Runner Label

The workflow file .github/workflows/e2e.yaml uses the "ubuntu-24.04-arm" label within the matrix strategy (specifically at line 14). Our repository search confirms that this label appears only in this file, and there’s no additional configuration indicating explicit support for it.

• File: .github/workflows/e2e.yaml (lines 10–15)
• Action Required: Manually verify that your self-hosted or cloud runner configuration accepts the custom label "ubuntu-24.04-arm". If it isn’t supported, update the label to a recognized one (e.g., "arm" or "arm64") to ensure that tests run correctly.

🧰 Tools

🪛 actionlint (1.7.4)

14-14: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)