Add isolated ops-warden warn pin (FLEX-WP-0016); FLEX-WP-0007 stays finished
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

policy.enabled cannot flip against the user-engine or tenant-engine
bindings. Helm release flex-auth-ops-warden rev 1 serves the production
registry in warn. Workstation warden sends no caller token; enforce and
the yaml flip stay ops-warden's.
This commit is contained in:
tegwick 2026-08-19 14:50:04 +02:00
parent c48c696387
commit 259f8a20a6
6 changed files with 142 additions and 2 deletions

22
values/ops-warden.yaml Normal file
View file

@ -0,0 +1,22 @@
# Independently rollable ops-warden signing-policy pin (FLEX-WP-0016).
# Isolated: no in-cluster PEP namespace yet. Workstation warden sign is not a
# Kubernetes ServiceAccount, so first mode is warn. Do not copy enforce from
# the user-engine/tenant-engine pins.
name: flex-auth-ops-warden
image:
repository: forgejo.coulomb.social/coulomb/flex-auth
digest: sha256:138aa3471c46bca6e814691fa1e6520aedda3dffd743e6b09141ab433afdb64b
args:
- serve
- --addr
- 0.0.0.0:8080
- --registry
- /opt/flex-auth/examples/ops-warden/production_registry_snapshot.json
- --policy
- /opt/flex-auth/examples/ops-warden/policy_package.md
callerAuth:
mode: warn
kubernetesURL: https://10.43.0.1
binding: ops-warden=system:serviceaccount:ops-warden:ops-warden
consumer:
isolated: true