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
8. Call out risks, unknowns, and decisions that need stakeholder input.
151
-
9. Assess **LSM compatibility** — if the change touches process identity, `/proc` filesystem access, binary execution, or inter-process visibility, flag whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. In particular, tests that fork+exec into system binaries will fail on SELinux-enforcing hosts due to cross-label `/proc/<pid>/exe` access restrictions.
151
+
9. Assess **gateway config documentation impact** — if the change adds, removes, renames, or changes defaults for gateway TOML keys or driver-specific config options, the plan must include an update to `docs/reference/gateway-config.mdx`. If the change is surfaced through Helm or a compute-driver overview, also include `docs/reference/sandbox-compute-drivers.mdx` or the relevant deployment docs.
152
+
10. Assess **LSM compatibility** — if the change touches process identity, `/proc` filesystem access, binary execution, or inter-process visibility, flag whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. In particular, tests that fork+exec into system binaries will fail on SELinux-enforcing hosts due to cross-label `/proc/<pid>/exe` access restrictions.
152
153
153
154
### A2: Post the Plan Comment
154
155
@@ -436,6 +437,13 @@ Review the documentation requirements in `AGENTS.md` and update any affected
436
437
docs as part of the implementation. Keep documentation changes scoped to the
437
438
behavior or subsystem that changed.
438
439
440
+
If the implementation changes gateway TOML parsing, `[openshell.gateway]`
441
+
fields, `[openshell.drivers.<name>]` fields, driver config defaults, or Helm
442
+
rendering of `gateway.toml`, update `docs/reference/gateway-config.mdx` in the
443
+
same branch. If the change affects user-facing compute-driver setup, also
444
+
update `docs/reference/sandbox-compute-drivers.mdx` or the relevant deployment
445
+
page.
446
+
439
447
### Step 12: Commit and Push
440
448
441
449
Commit all changes using conventional commit format. The `<type>` comes from the issue type in the plan:
Copy file name to clipboardExpand all lines: .agents/skills/create-spike/SKILL.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,9 +91,11 @@ The prompt to the reviewer **must** instruct it to:
91
91
92
92
9.**Check architecture docs** in the `architecture/` directory for relevant documentation about the affected subsystems.
93
93
94
-
10.**Assess Linux Security Module (LSM) impact.** If the change involves process identity, `/proc` filesystem access, file labeling, binary execution, or inter-process visibility, call out whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. For example: reading `/proc/<pid>/exe` across an SELinux domain boundary returns ENOENT, not EACCES. Tests that fork+exec into system binaries (different SELinux label) will fail on enforcing hosts. Flag any LSM-sensitive code paths and recommend mitigations.
94
+
10.**Assess gateway config documentation impact.** If the change would add, remove, rename, or change defaults for gateway TOML keys or driver-specific config options, call out that `docs/reference/gateway-config.mdx` must be updated. If the change is surfaced through Helm or compute-driver setup docs, call out the relevant deployment or compute-driver docs too.
95
95
96
-
11.**Determine the issue type:**`feat`, `fix`, `refactor`, `chore`, `perf`, or `docs`.
96
+
11.**Assess Linux Security Module (LSM) impact.** If the change involves process identity, `/proc` filesystem access, file labeling, binary execution, or inter-process visibility, call out whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. For example: reading `/proc/<pid>/exe` across an SELinux domain boundary returns ENOENT, not EACCES. Tests that fork+exec into system binaries (different SELinux label) will fail on enforcing hosts. Flag any LSM-sensitive code paths and recommend mitigations.
97
+
98
+
12.**Determine the issue type:**`feat`, `fix`, `refactor`, `chore`, `perf`, or `docs`.
Copy file name to clipboardExpand all lines: .agents/skills/debug-openshell-cluster/SKILL.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,6 +138,15 @@ kubectl -n openshell rollout status statefulset/openshell
138
138
139
139
Look for failed installs, unexpected values, missing namespace, wrong image tag, TLS settings that do not match the registered endpoint, and scheduling failures.
140
140
141
+
For HA or PostgreSQL-backed installs, also check the service-binding Secret and
142
+
bundled PostgreSQL workload:
143
+
144
+
```bash
145
+
kubectl -n openshell get secret -l app.kubernetes.io/instance=openshell
146
+
kubectl -n openshell get statefulset,pod,pvc -l app.kubernetes.io/instance=openshell
Copy file name to clipboardExpand all lines: .agents/skills/helm-dev-environment/SKILL.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: helm-dev-environment
3
-
description: Start up, tear down, and configure the local Kubernetes development environment for OpenShell. Uses k3d (Docker-backed k3s) + Skaffold + Helm. Covers cluster lifecycle, optional add-ons (Keycloak OIDC, Envoy Gateway), and port mappings. Trigger keywords - local k8s, local cluster, k3d, skaffold, helm dev, start cluster, stop cluster, tear down cluster, delete cluster, create cluster, helm:k3s, helm:skaffold, local dev environment, dev cluster, k8s dev, envoy gateway local, keycloak local.
3
+
description: Start up, tear down, and configure the local Kubernetes development environment for OpenShell. Uses k3d (Docker-backed k3s) + Skaffold + Helm. Covers cluster lifecycle, optional add-ons (Keycloak OIDC, Envoy Gateway), HA testing, and port mappings. Trigger keywords - local k8s, local cluster, k3d, skaffold, helm dev, start cluster, stop cluster, tear down cluster, delete cluster, create cluster, helm:k3s, helm:skaffold, local dev environment, dev cluster, k8s dev, envoy gateway local, keycloak local, high availability, HA.
4
4
---
5
5
6
6
# Helm Dev Environment
@@ -65,6 +65,10 @@ generates mTLS secrets on first install. Envoy Gateway opt-in; see the Optional
65
65
66
66
The gateway Service uses ClusterIP. Access is via Envoy Gateway (port `8080`) or `kubectl port-forward`.
67
67
68
+
**HA test deploy** (two gateway replicas + bundled PostgreSQL): uncomment
69
+
`#- ci/values-high-availability.yaml` in `deploy/helm/openshell/skaffold.yaml`,
70
+
then run `mise run helm:skaffold:run` or `mise run helm:skaffold:dev`.
71
+
68
72
### TLS behaviour
69
73
70
74
`ci/values-skaffold.yaml` sets `server.disableTls: true`, so Skaffold-based deploys run
@@ -198,6 +202,7 @@ mise run helm:k3s:status
198
202
|`deploy/helm/openshell/ci/values-skaffold.yaml`| Dev overrides (image pull policy, TLS disabled for local Skaffold) |
0 commit comments