You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 36ad7f2
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/helm-dev-environment/SKILL.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -445,6 +445,16 @@ public `SandboxStatus` image fields. Resume a pending operation with
445
445
`SandboxUpdates.UpdateSandbox`, the current resource version, and no selected
446
446
fields, following the documented request-ID semantics.
447
447
448
+
449
+
For the opt-in application listener, build/import matching branch images and run
450
+
`mise run e2e:kubernetes:app-listener`; see `e2e/kubernetes/app-listener/README.md`
451
+
for image, topology, delivery-mode and takeover inputs. The task owns an isolated
452
+
Helm release/namespace, temporary TLS material, in-cluster clients, teardown and
453
+
evidence under `results/app-listener/`. It checks policy denial, Pod-IP ingress without app Services, shared-owner takeover, gateway-outage expiry and disabled-listener
454
+
gateway compatibility, without discovery or a proxy. CI runs four cases under
455
+
`test:e2e`and includes them in `Core E2E result`. Its reusable kind setup installs
456
+
pinned Calico only for this lane; other jobs retain kindnet. Local k3s already
457
+
enforces policy. The lower-level `verify.py` can target a predeployed release.
448
458
The kube e2e wrapper creates only one port-forward, to `svc/openshell`; it no
449
459
longer forwards the unauthenticated health listener or runs a `/readyz` e2e
450
460
target. `/readyz` remains covered by server unit/integration tests.
@@ -645,3 +655,14 @@ identity and contents, command/environment changes, and request replay.
645
655
`OPENSHELL_E2E_UPDATE_ORIGINAL_IMAGE`and `OPENSHELL_E2E_UPDATE_TARGET_IMAGE` can
646
656
select mirrored Alpine 3.21 and 3.22 manifests. Defaults use the public registry
647
657
cache; keep immutable digests when overriding them.
658
+
659
+
## App listener fixture
660
+
661
+
The opt-in `deploy/helm/openshell/ci/values-app-listener.yaml` enables the
662
+
supervisor listener at port 9443 without discovery or a proxy. Provision the
663
+
operator TLS Secret and an ingress-client NetworkPolicy first. Follow
664
+
`e2e/kubernetes/app-listener/README.md`for direct in-cluster verification,
665
+
shared-member selection, and the HA follow-up checks. Keep the fixture disabled
666
+
in default profiles. Dedicated and shared supervisors expose app ports on their
667
+
Pod IPs without app Services. Select the member owning the sandbox; automatic
668
+
owner selection belongs to the later discovery API.
Copy file name to clipboardExpand all lines: .agents/skills/release-openshell/SKILL.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,3 +83,11 @@ updating a Snap Store support track. Docs retain an
83
83
immutable version and advance latest only for a newer version.
84
84
85
85
Watch the stable release run and report its result.
86
+
87
+
## PyPI publishing
88
+
89
+
Stable releases publish the built Python wheel directly to PyPI from the `publish-pypi` job in `release.yml`, after the other release publishers succeed. The job downloads the wheel from the stable GitHub Release, not the run's build artifact, and checks the stable tag's source commit and the wheel's release checksum. It uses Trusted Publishing with the `pypi` GitHub environment. Configure the `openshell` PyPI project's GitHub publisher with owner `NVIDIA`, repository `OpenShell`, workflow `release.yml`, and environment `pypi`. No PyPI API token or GitLab trigger credentials are required.
90
+
91
+
The environment must allow the branch used to dispatch Release. For a support release, explicitly allow its support branch before dispatching. Required reviewers, if configured, must approve the PyPI job. Stable docs publish after PyPI succeeds. An existing wheel on PyPI is skipped when retrying Release; PyPI does not allow replacing a published wheel. Because the job publishes the release asset, a new Release run for the same tag can finish a failed PyPI upload.
92
+
93
+
Development and prerelease wheels remain GitHub Release assets and do not publish to PyPI.
Copy file name to clipboardExpand all lines: .agents/skills/watch-github-actions/SKILL.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,13 @@ gh run list --json databaseId,status,headBranch,url --jq '.[] | {id: .databaseId
125
125
126
126
## View Job Logs
127
127
128
-
For tmachine Kubernetes conformance failures, inspect the `e2e-results-conformance-sandbox-ubuntu-k3s-*` artifact. Its `diagnostics/` holds the K3s report with Agent Sandbox controller state, leader leases, events, and current and previous controller logs. The k3s installers check reconciliation after guest boot with a temporary scheduling-gated Sandbox probe, so a failed probe fails provisioning before any test runs. Distinguish a failed controller probe from a failed conformance scenario; gateway connectivity and controller Deployment availability do not prove reconciliation works.
128
+
For Kubernetes app-listener E2E failures during kind setup, inspect the uploaded
129
+
`results/app-listener/cni-setup/` evidence. It includes node and Calico pod
130
+
descriptions, events, and current/previous container logs. A CNI rollout timeout
131
+
occurs before the listener tests run; use these diagnostics to distinguish image
132
+
pulls, init failures, and readiness failures.
133
+
134
+
For tmachine Kubernetes conformance failures, inspect the `e2e-results-conformance-conformance-ubuntu-k3s-*` artifact. Its `diagnostics/` holds the K3s report with Agent Sandbox controller state, leader leases, events, and current and previous controller logs. The k3s installers check reconciliation after guest boot with a temporary scheduling-gated Sandbox probe, so a failed probe fails provisioning before any test runs. Distinguish a failed controller probe from a failed conformance scenario; gateway connectivity and controller Deployment availability do not prove reconciliation works.
129
135
130
136
For the `e2e-suites` lane (`.github/workflows/e2e-suites.yml`), the last lines of the job log give the runner's result: PASS, FAIL (exit 1) after the end of the nextest log (which names the failed tests), or ERROR (exit 2) with the step that broke. FAIL and ERROR also appear as annotations on the run's summary page. Then inspect the `e2e-results-<family>-<package>-<environment>-<installer>` artifact, which holds `junit.xml`, `nextest.log` and, after a failure, the guest's `diagnostics/`.
description: Report an OpenShell vulnerability privately using the required advisory template.
5
+
body:
6
+
- type: markdown
7
+
attributes:
8
+
value: |
9
+
Follow [SECURITY.md](https://github.com/NVIDIA/OpenShell/blob/main/SECURITY.md) and the [advisory template](https://github.com/NVIDIA/OpenShell/blob/main/.agents/skills/create-security-advisory/assets/advisory-template.md).
10
+
11
+
Review the report and verify its accuracy before submitting. Distinguish reproduced behavior, code inspection, and unverified claims. Remove secrets and personal information from evidence.
12
+
13
+
- type: textarea
14
+
id: summary-and-impact
15
+
attributes:
16
+
label: Summary and impact
17
+
description: Describe what the attacker can do, which security boundary should prevent it, and the demonstrated impact. Separate unverified consequences.
18
+
placeholder: Summarize the vulnerability and its impact in two or three sentences.
19
+
validations:
20
+
required: true
21
+
22
+
- type: textarea
23
+
id: scope-and-prerequisites
24
+
attributes:
25
+
label: Scope and prerequisites
26
+
description: Include each item below. Separate the tested revision from confirmed affected releases. For unknowns, state what needs checking.
27
+
placeholder: |
28
+
- Product and tested version: Component, release or full commit SHA; image digest if relevant.
29
+
- Affected versions: Confirmed release range and evidence, or Unknown with the needed check.
30
+
- Environment and configuration: Relevant OS, runtime/driver, topology, and exact settings; default or opt-in.
31
+
- Attacker access: Starting privileges, controlled input, and resources in scope.
32
+
validations:
33
+
required: true
34
+
35
+
- type: textarea
36
+
id: reproduction-and-evidence
37
+
attributes:
38
+
label: Reproduction and evidence
39
+
description: Provide reproduction steps and observed results, or concrete code evidence of the attack path. State what was verified and what was not run; scanner output alone is insufficient.
40
+
placeholder: |
41
+
Verification status: Reproduced / code inspection only / reporter claim not reproduced.
42
+
43
+
1. Operator setup: Minimal prerequisites, test resources, and copyable commands/configuration.
44
+
2. Attacker actions: Exact steps under the privileges stated above.
45
+
3. Check: Read back the response or state change that demonstrates the impact.
46
+
47
+
Expected: Security-preserving behavior; link the applicable policy, contract, or enforcing code.
48
+
Observed: Actual result and concise redacted output; if not executed, say so.
49
+
50
+
Link the source report, private artifacts, and relevant code at an immutable revision.
51
+
State who verified what and any failed attempts or limitations.
52
+
validations:
53
+
required: true
54
+
55
+
- type: textarea
56
+
id: additional-details
57
+
attributes:
58
+
label: Additional details
59
+
description: Include supported optional details that help review. Leave blank if none are available.
60
+
placeholder: |
61
+
Root cause, severity rationale and CVSS/CWE, existing CVE identifiers,
62
+
disclosure deadlines, a proposed fix or verified workaround, known
63
+
unaffected deployments, or a related private PR.
64
+
validations:
65
+
required: false
66
+
67
+
- type: textarea
68
+
id: open-questions
69
+
attributes:
70
+
label: Open questions
71
+
description: List missing evidence that affects the assessment and the next check for each gap. Leave blank if there are no known gaps.
0 commit comments