Files
puppet-prod/site/profiles/templates
unkin-agent 9db9afae8d
ci/woodpecker/pr/ruby-validate Pipeline was successful
ci/woodpecker/pr/puppet-lint Pipeline was successful
ci/woodpecker/pr/bolt-validate Pipeline was successful
ci/woodpecker/pr/yamllint Pipeline was successful
ci/woodpecker/pr/erb-validate Pipeline was successful
ci/woodpecker/pr/epp-validate Pipeline was successful
ci/woodpecker/pr/puppet-validate Pipeline was successful
ci/woodpecker/pr/ruby-check Pipeline was successful
Let certmanager and sshsignhost authenticate to Vault by kubernetes auth
Both helpers are run server-side by generate() during catalog compilation and
only speak AppRole, whose token_bound_cidrs pin them to the six legacy VM
masters, so the autoscaled k8s compilers cannot obtain a token and any compile
needing a cert or a signed host key fails there.

- Add a kubernetes login branch that reads the service account JWT and posts it
  to auth/<k8s_mount>/login, selected by an auth_method config key
- Add auth_method, k8s_mount, k8s_role and jwt_path class parameters, defaulting
  to approle so the VM masters render and behave as before
- Render role_id and approle_path only for the approle case
- Report a missing JWT, a rejected login or an unknown auth_method on stderr
  instead of falling back or raising
- Point sshsignhost at the sshca mount and signhost role that Vault actually has

Needs terraform-vault #152, already applied.
2026-09-13 23:06:32 +10:00
..
2025-07-06 20:02:20 +10:00
2026-01-03 21:51:47 +11:00
2024-04-06 03:27:45 +11:00
2024-11-16 19:54:19 +11:00
2024-07-06 22:02:00 +10:00
2024-01-05 21:44:41 +11:00
2025-06-15 17:43:19 +10:00
2024-06-02 19:32:02 +10:00
2024-05-25 14:18:56 +10:00
2024-05-22 22:05:54 +10:00
2024-06-09 20:26:34 +10:00
2023-12-03 18:05:01 +11:00