Deploy arrproxy v0.2.0 machine-mint admin route #384
Reference in New Issue
Block a user
Delete Branch "benvin/arrproxy-v0.2.0-admin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The future Vault engine needs to machine-mint arrproxy tokens without an interactive Authentik session. arrproxy v0.2.0 adds an admin route (
POST /api/admin/...) protected by its own bearer token; OpenBao running on the VMs calls it through the arrstack ingress. This deploys that route.Changes
arrproxy-admin-tokenVaultStaticSecret (mirrors thearrproxy-pepperVSO: samedefaultVaultAuth, k8s-auth default-SA pattern) syncingkv/kubernetes/namespace/arrstack/default/arrproxy-admin-tokeninto thearrproxy-admin-tokenSecret. The token is seeded in Vault KV as the shared source of truth for the future Vault engine.ARRPROXY_ADMIN_TOKENon the arrproxy-api Deployment viasecretKeyRef(keytoken), and addarrproxy-admin-tokento the Reloadersecret.reloader.stakater.com/reloadannotation so the pod rolls on rotation./api/admin/route in oauth2-proxy:OAUTH2_PROXY_SKIP_AUTH_REGEXbecomes^/[^/]+/api,^/api/admin/. The admin route is intentionally oauth-skipped because it is protected by arrproxy's OWN bearer token so OpenBao can reach it machine-to-machine./api/tokensand/api/meare NOT matched and stay oauth-gated./api/admin/*already routes to the arrproxy-api upstream via the existing catch-all/api/upstream, so no upstream change is needed.v0.2.0(kept in lockstep).Validation
kustomize build --enable-helm apps/overlays/au-syd1/arrstacksucceeds.