hermes-bot
6f1a7b6d96
Folds the good parts of #1412 into this PR and addresses both review-bot reviews (#1412 review 1789, #1414 review 1791): - Everything after the OpenBao store is best-effort. Decode, reconnect, listing and revokes run in reap_superseded(); reap_summary() turns any error into "reap skipped" plus a warning, so rotate_ha_token returns Ok. A failed run would start a second pod (backoffLimit: 1) that keeps the token just stored and its successor and reaps the token consumers still hold until ESO syncs, i.e. the #1081 outage. Two unit tests cover it. - Warn when the replaced token is not named "<client_name> [<6 hex>]": no later run reaps it, so it needs a manual revoke (from #1412). - Staged image rollout (from #1412): only the three HA CronJobs carry the flux-system:secret-rotator marker; the other 17 rotators stay on 2026-07-30 until a manual HA run validates the new binary, then a follow-up adds the marker to them. rotation/kustomization.yaml records the exception. - Merged current main (a6f37e2b,1691a0ac): the Reloader annotations for zone-configurator and speech-to-phrase are already there via #1409.
96 lines
3.5 KiB
YAML
96 lines
3.5 KiB
YAML
---
|
|
# Class-B rotation of the gitea PAT Flux uses as its git credential (the
|
|
# dedicated 'flux' service account). Runs the secret-rotator binary (gitea-token
|
|
# mode): mint a new PAT via basic auth, VERIFY it can pull AND push (Flux
|
|
# image-automation writes back), store it, and reap old tokens keeping the two
|
|
# newest. A token that fails verification is deleted and the run aborts without
|
|
# storing, so Flux is never stranded.
|
|
#
|
|
# gitea is reached at the in-cluster Service gitea.gitea.svc:3000 — the public
|
|
# name hairpins off the ingress LB from a pod. Needs BOTH netpol halves
|
|
# (gitea-allow-flux-rotator + rotator-gitea-flux-egress).
|
|
#
|
|
# The ExternalSecret that publishes the rotated token to Flux lives in
|
|
# ../../post-crds/flux-git-externalsecret.yaml (needs ESO's CRDs).
|
|
---
|
|
apiVersion: v1
|
|
kind: ServiceAccount
|
|
metadata:
|
|
name: gitea-flux-secret-rotator
|
|
namespace: openbao
|
|
labels:
|
|
app.kubernetes.io/name: flux-git
|
|
app.kubernetes.io/component: secret-rotator
|
|
---
|
|
apiVersion: batch/v1
|
|
kind: CronJob
|
|
metadata:
|
|
name: flux-git-secret-rotate
|
|
namespace: openbao
|
|
labels:
|
|
app.kubernetes.io/name: flux-git
|
|
app.kubernetes.io/component: secret-rotator
|
|
spec:
|
|
suspend: false
|
|
schedule: "0 4 1 1,4,7,10 *" # quarterly, Europe/Berlin
|
|
timeZone: Europe/Berlin
|
|
concurrencyPolicy: Forbid
|
|
successfulJobsHistoryLimit: 2
|
|
failedJobsHistoryLimit: 5
|
|
startingDeadlineSeconds: 3600
|
|
jobTemplate:
|
|
spec:
|
|
backoffLimit: 1
|
|
activeDeadlineSeconds: 300
|
|
ttlSecondsAfterFinished: 259200 # 3 d
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app.kubernetes.io/name: flux-git
|
|
app.kubernetes.io/component: secret-rotator
|
|
spec:
|
|
serviceAccountName: gitea-flux-secret-rotator
|
|
restartPolicy: Never
|
|
securityContext:
|
|
runAsNonRoot: true
|
|
runAsUser: 65534
|
|
runAsGroup: 65534
|
|
seccompProfile:
|
|
type: RuntimeDefault
|
|
containers:
|
|
- name: rotate
|
|
image: gitea.renner.uno/gitea_admin/secret-rotator:2026-07-30
|
|
args: ["gitea-token"]
|
|
securityContext:
|
|
allowPrivilegeEscalation: false
|
|
readOnlyRootFilesystem: true
|
|
capabilities:
|
|
drop: ["ALL"]
|
|
env:
|
|
- name: BAO_ADDR
|
|
value: http://openbao.openbao.svc.cluster.local:8200
|
|
- name: BAO_ROLE
|
|
value: rotator-gitea-flux
|
|
- name: BOOTSTRAP_PATH
|
|
value: homelab/infrastructure/secret-rotators-bootstrap/gitea-flux
|
|
- name: BAO_PATH
|
|
value: homelab/infrastructure/flux-git
|
|
- name: GITEA_URL
|
|
value: http://gitea.gitea.svc.cluster.local:3000
|
|
- name: GITEA_VERIFY_REPO
|
|
value: konairius/homelab
|
|
- name: GITEA_SCOPES
|
|
value: write:repository
|
|
# Load-bearing: konairius/homelab is public, so the pull check
|
|
# passes for ANY valid token — push (git-receive-pack, needs
|
|
# write) is the only real verification. Pinned explicitly so the
|
|
# safety property is visible here, not just a binary default.
|
|
- name: GITEA_REQUIRE_PUSH
|
|
value: "true"
|
|
resources:
|
|
requests:
|
|
cpu: 25m
|
|
memory: 16Mi
|
|
limits:
|
|
memory: 48Mi
|