ci(qualification): add Ubuntu 24.04 k3s scenario
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, kubernetes, rust, ubuntu
- Domain
- ci-cd, devops, infrastructure, testing-qa
Research direction
Start by reading the shared qualification interface and installation profile model, then inspect the existing tmachine and GitHub Actions entry points for Docker and Podman scenarios. The work is complete when an Ubuntu 24.04 guest with pinned k3s provisions and cleans up reliably, exposes cluster inputs, composes with the profile and testsuite, and emits safe diagnostics.
Written by the indexing model from the issue text.
Description
Description
Add an Ubuntu 24.04 k3s scenario for Kubernetes release qualification. The scenario provisions a disposable Ubuntu guest and a pinned k3s version, then exposes the cluster inputs needed by independently selected OpenShell installation profiles and testsuites.
The scenario owns guest and cluster setup only. It must not embed OpenShell installation or conformance behavior.
Context
- Parent release pipeline: #2860
- Native-install proof-of-concept pipeline: #2976
- Shared driver conformance suite: #2183
- Reusable QEMU guest infrastructure: #2471
- Installation profile model: #3419
This follows the initial Docker and Podman proof of concept and extends the same qualification composition model to a local Kubernetes environment.
Definition of Done
- The scenario provisions Ubuntu 24.04 with a pinned, supported k3s/Kubernetes version.
- The cluster is ready before qualification begins, and its effective Kubernetes version and node state are reported.
- The scenario exposes kubeconfig and cluster inputs through the shared qualification interface without embedding OpenShell installation behavior.
- The scenario can compose with the applicable OpenShell installation profile and shared conformance testsuite.
- The scenario can be invoked locally through
tmachineand from GitHub Actions. - Failure artifacts include relevant guest, systemd, k3s, Kubernetes, gateway, and sandbox diagnostics without secrets.
- Cleanup removes the disposable guest and cluster state after successful, failed, and interrupted runs.
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/OpenShell
-
area:docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:cli state:validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
state:triage-needed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:build spike state:review-ready state:stale
Difficulty 2/5 Half a day Newbie friendliness 68/100
All issues in NVIDIA/OpenShell
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100