jakman85andClaude Opus 5
c5b5b8672a
A service that reads this repository's Gitea issues, decides what to do about each thread as the Program Manager persona, and runs one worker agent per assignment that authors a change, runs the merge gate and opens a pull request. It reacts to issue creation and to comments; the assignment and all correspondence travel through the issue thread and the PR. It authenticates with an Anthropic subscription token. It never pushes to main and never merges. Three choices carry the design, with alternatives recorded in docs/plans/: - it POLLS rather than receiving webhooks (Gitea's webhook SSRF guard, lost deliveries, and no inbound reach needed at all); - it keeps NO state: the trigger is "the newest thing in this thread was not written by me", so the issue thread is the state — no PVC, no backup obligation; - the model holds NO tools: its reply is one JSON object this code validates, so nothing in the path executes text. The boundary is platform/kyverno/admission/pm-agent-job-shape.yaml (Enforce, failurePolicy: Fail), not the RBAC: Kubernetes places no `use` check on serviceAccountName, so "may create Jobs" is "may run arbitrary code as the namespace's most privileged identity". Six rules admit only the committed shape, and the worker identity is bound to nothing with no token mounted, so there is nothing to escalate to. 28/28 offline Kyverno assertions. Nothing has run: the image has never been built or pushed, and both the image digest and the two credentials are deliberate placeholders. See the handoff entry's "What I did NOT verify". Refs CLAUDE.md §1/§3/§6, R-SEC-02, R-GITOPS-02. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
42 lines
2.3 KiB
YAML
42 lines
2.3 KiB
YAML
---
|
|
# pm-agent — the Program Manager agent service. Reconciled by its OWN post-platform Flux
|
|
# Kustomization (clusters/base/pm-agent.yaml, dependsOn apps-wave-0, wait:false), NOT by the
|
|
# gating `platform` tier.
|
|
#
|
|
# WHY ITS OWN NON-GATING TIER, like crafty/headlamp/homepage: this is a leaf whose pod can be
|
|
# legitimately unhealthy for a long time — it CrashLoops by design while its credentials are
|
|
# still placeholders, and it depends on Gitea being up (apps-wave-0) to authenticate at
|
|
# startup. A workload like that inside the gating `platform` tier would keep `platform`
|
|
# not-Ready, and while `platform` is not-Ready NOTHING downstream reconciles. That is the
|
|
# headlamp gating stall, and it is not worth re-learning.
|
|
#
|
|
# dependsOn apps-wave-0 rather than platform-config: what this service actually needs is
|
|
# GITEA, not the Keycloak realm, the wildcard certificate or the Gateway — it serves no
|
|
# traffic and has no UI.
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- namespace.yaml
|
|
# The dispatcher identity (may create worker Jobs here) and the worker identity (bound to
|
|
# nothing). Read alongside platform/kyverno/admission/pm-agent-job-shape.yaml: that policy
|
|
# is the boundary, this file is only its necessary half.
|
|
- rbac.yaml
|
|
- configmap.yaml
|
|
# The Gitea token and the Anthropic subscription token — SOPS-encrypted, decrypted
|
|
# per-environment by the pm-agent Kustomization (clusters/prod and clusters/dev patch it by
|
|
# name, identically to crafty/headlamp/oauth2-proxy). Referenced by name only (R-IDP-04).
|
|
#
|
|
# THE COMMITTED VALUES ARE PLACEHOLDERS. The service is inert until the operator replaces
|
|
# them; the hand-off steps are in the sibling `.example` template and in README.md.
|
|
#
|
|
# That template is named in prose rather than by filename ON PURPOSE: the L0 check
|
|
# no-plaintext-secrets treats a mention of an unencrypted `.example` in a kustomization as
|
|
# a REFERENCE and refuses it as a plaintext Secret that would be applied. It is right to —
|
|
# the distance between naming a file in a comment and listing it under `resources:` is one
|
|
# careless edit.
|
|
- pm-agent-credentials.sops.yaml
|
|
- deployment.yaml
|
|
# default-deny baseline + the two egress allow policies (gitea, kube-apiserver for the
|
|
# dispatcher only, tcp/443 for the model). NO ingress allow exists, by design.
|
|
- networkpolicy.yaml
|