ProofedMesh/deploy/approval-service/10-secret-dev.example.yaml
CTO (Paperclip) 20ba29d3ac
All checks were successful
build-images / signing-service image (push) Successful in 26s
build-images / verification-service image (push) Successful in 27s
build-images / approval-service image (push) Successful in 31s
build-images / dummy-sink image (push) Successful in 29s
validate / JSON Schema (ajv) (push) Successful in 23s
validate / Rego (opa fmt + opa test) (push) Successful in 16s
phase1-smoke / Phase 1 end-to-end smoke (push) Successful in 1m0s
validate / DB (migrate up/down dry-run) (push) Successful in 26s
validate / Go (vet + test) (push) Successful in 1m20s
approval-service: K8s deployment manifests + Pocket-ID OIDC client (DEV-614)
Phase-1 Subtask 8/10 (parent DEV-606):
- deploy/approval-service/: SA (no auto-mount), Deployment (replicas=2,
  distroless-nonroot, read-only rootfs), ClusterIP :8080, NetworkPolicy
  (ingress from pangolin namespace only; egress to signing-service,
  transparency-log, trust-pg in agent-trust + pocket-id + DNS), README.
- 10-secret-dev.example.yaml template + the real 10-secret-dev.sealed.yaml
  carrying the Pocket-ID client id/secret, WebAuthn RP config, and the
  dev signing-service bearer; unsealed in-cluster to Secret
  approval-service-dev.
- services/approval-service/Dockerfile: BuildKit multi-stage, context-at-
  repo-root, matches the signing/verification/dummy-sink pattern.
- .forgejo/workflows/build-images.yml: new approval-service job pushing
  harbor.basicstack.de/basicstack/approval-service:{sha,main} on main.
- Pocket-ID: created proofedmesh-admin group + OIDC client
  "ProofedMesh Approval" with PKCE enforced, callback
  https://approval.proofedmesh.basicstack.de/oidc/callback, group
  restriction to proofedmesh-admin. Client secret stored as Paperclip
  secret proposal and in the SealedSecret above — never pasted inline.

Deployment applied cluster-side pending the first CI image build:
`kubectl apply -f deploy/approval-service/` is green; pods ErrImagePull
until the Forgejo workflow completes and pushes the :main tag.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-10-25 21:12:01 +00:00

32 lines
1.4 KiB
YAML

# approval-service dev secret — EXAMPLE ONLY.
#
# This file is a template. The real cluster secret MUST be created either
# as a SealedSecret (preferred, see deploy/approval-service/README.md) or
# applied imperatively with values that never land in the git repo.
#
# Secret shape:
# APPROVAL_SIGNING_TOKEN — Bearer token the approval-service presents
# to the signing-service (dev: match the
# `SIGNING_BEARERS` entry on signing-service)
# APPROVAL_POCKET_ID_CLIENT — Pocket-ID OIDC client ID (returned by the
# client registration in README)
# APPROVAL_POCKET_ID_SECRET — Pocket-ID OIDC client secret
# APPROVAL_WEBAUTHN_RP_ID — relying party ID shown to the browser
# APPROVAL_WEBAUTHN_RP_ORIGIN — allowed origin for client_data_json
#
apiVersion: v1
kind: Secret
metadata:
name: approval-service-dev
namespace: agent-trust
labels:
app.kubernetes.io/name: approval-service
app.kubernetes.io/part-of: proofedmesh
proofedmesh.basicstack.de/mode: dev
type: Opaque
stringData:
APPROVAL_SIGNING_TOKEN: "REPLACE_WITH_SIGNING_SERVICE_BEARER"
APPROVAL_POCKET_ID_CLIENT: "REPLACE_WITH_POCKET_ID_CLIENT_ID"
APPROVAL_POCKET_ID_SECRET: "REPLACE_WITH_POCKET_ID_CLIENT_SECRET"
APPROVAL_WEBAUTHN_RP_ID: "approval.proofedmesh.basicstack.de"
APPROVAL_WEBAUTHN_RP_ORIGIN: "https://approval.proofedmesh.basicstack.de"