Authenticating the Cordium Genesis Cleanup Hook
The recent commit adds documentation and CI checks that ensure the Cordium genesis cleanup hook authenticates using the cluster’s in‑cluster credentials and respects a 120‑second deadline, preventing unauthorized identity recreation.
Documentation Clarifies Cleanup Job Security Context
Three lines were added to docs/octelium.md describing that the cleanup Job runs with kubectl’s default in‑cluster token and CA, enforces a 120‑second Job deadline, and removes any request‑timeout override so kubectl can select the mounted identity. The prose also instructs reviewers to verify that the three genesis resources are absent after a reviewed child sync.
CI Enforcement of Deadline and Authenticated Execution
The scripts/ci/offline-static-checks.sh file now includes a static check that the cleanup Job’s activeDeadlineSeconds equals 120 and that the container does not use a custom command. Additionally, the --request-timeout=30s argument was removed from the command list, ensuring the Job runs with the expected security context.
Verification Path and Next Steps
To confirm the changes, a team should trigger a synthetic child sync, let the cleanup Job execute, and inspect the Job logs to ensure it uses the in‑cluster token and terminates within the 120‑second window. This same pattern can be applied to other GitOps homelabs that need to guarantee cleanup jobs run with the correct credentials and timeout constraints.