Iter-6 E-03 + E-04: pin image to NAS, add PSA-restricted security context (with documented s6 exception)#1
Merged
Merged
Conversation
Audit F-1: image.tag was `latest`. Pin to 2026.05-rc1 (only NAS tag; no v-semver alias yet) and repath to NAS. Iter-8 flips back to ghcr.io. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The Gitea image GitClaw wraps uses s6-svscan, which requires UID 0 at start to open /etc/s6/.s6-svscan/lock; it drops to UID 1000 via s6-setuidgid before running gitea. This blocks PSA-restricted admission for this chart. Documented as the chart's canonical exception (PLAN-06 E-04 / audit F-4): values.yaml comment names the constraint and lists the three operator options (separate baseline namespace / swap image / disable chart). The container-level 'containerSecurityContext' key is added (empty default) so consumers can layer in overrides without changing the template. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ing) The SAO umbrella's bp-001 Chart.yaml depends on gitclaw 0.1.2 (the prior vendored version). Bumping to 0.1.3 so the SAO bundle can pin to the version that carries the iter-6 fixes (NAS-pinned image, PSA security-context block with documented s6 exception). SAO will update its dependency line to 0.1.3 in the same PR cycle. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…0.1.3->0.1.4 The chart's deployment.yaml mounts /data via persistentVolumeClaim when .Values.persistence.enabled is true, but the chart shipped no PVC manifest of its own. helm install + helm upgrade then fail with 'persistentvolumeclaim not found' on the gitclaw Pod. Re-add the PVC template (originally landed as PLAN-01 P27 but apparently lost in a rebase / squash somewhere) so the chart is self-contained again. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
image.tagwaslatest. Pin to2026.05-rc1(only existing NAS tag) and repath repository fromghcr.io/kafclaw/gitclawto192.168.0.131:5100/scalytics/gitclaw. Public ghcr.io publishing happens in Iter-8.podSecurityContext+containerSecurityContextkeys with a documented exception: the upstream Gitea image's s6-svscan needs UID 0 to open/etc/s6/.s6-svscan/lockbefore dropping privileges vias6-setuidgid. This blocks PSA-restricted admission. Operators needing PSA-restricted must (a) deploy GitClaw to a separate namespace atbaselinelevel, (b) replace the Gitea image, or (c) disable the chart. The constraint is named in thevalues.yamlcomment with the relevant past incident (PLAN-01 P27).Tracking
Test plan
helm template gitclaw charts/gitclawrenders the newsecurityContextblock on the main container (block is empty by default — values comment explains why)helm template gitclaw charts/gitclawrenders the newimage.repository: 192.168.0.131:5100/scalytics/gitclawandimage.tag: 2026.05-rc1🤖 Generated with Claude Code