vlogs: accept Vault identity JWTs and run oauth2-proxy HA #587

Merged
benvin merged 1 commits from benvin/vlogs-vault-jwt into main 2026-11-16 21:30:40 +11:00
Member

Agents need programmatic vlogs access with short-lived Vault identity OIDC tokens, and the oauth2-proxy runs as a single replica.

  • accept Vault identity JWT bearer tokens (audience victorialogs) via extra JWT issuer
  • run oauth2-proxy with 2 replicas spread across nodes
  • add a PodDisruptionBudget (minAvailable 1)

requires terraform-vault #179 applied first

Agents need programmatic vlogs access with short-lived Vault identity OIDC tokens, and the oauth2-proxy runs as a single replica. - accept Vault identity JWT bearer tokens (audience `victorialogs`) via extra JWT issuer - run oauth2-proxy with 2 replicas spread across nodes - add a PodDisruptionBudget (minAvailable 1) requires terraform-vault #179 applied first
unkin-agent added 1 commit 2026-11-16 20:49:12 +11:00
vlogs: accept Vault identity JWTs and run oauth2-proxy HA
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
9f56c3ce03
Author
Member
  • apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — blocking: extra-JWT issuer discovery runs at startup with the default HTTP client (context.TODO, http.DefaultTransport), which ignores OAUTH2_PROXY_PROVIDER_CA_FILES. vault.service.consul:8200 is internal-CA signed, so discovery and the JWKS fallback both fail and oauth2-proxy exits "error building verifiers" → crash loop on both replicas, human OIDC login included → add SSL_CERT_FILE: "/etc/ssl/combined/ca-certificates.crt" to the configmap (the combined bundle is already mounted).
  • apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — blocking: OAUTH2_PROXY_ALLOWED_GROUPS=akP-vlogs-admin is still enforced on bearer sessions (provider.Authorize), with groups read from the ak_groups claim. A Vault identity token has no such claim unless the terraform-vault #179 role template emits ak_groups: ["akP-vlogs-admin"] → confirm #179 sets it, otherwise every Vault JWT gets 403.
  • apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — nit: startup now hard-depends on Vault being reachable (verifier build fails the pod if Vault is down) → accept explicitly or note in the PR body.
- apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — blocking: extra-JWT issuer discovery runs at startup with the default HTTP client (context.TODO, http.DefaultTransport), which ignores OAUTH2_PROXY_PROVIDER_CA_FILES. vault.service.consul:8200 is internal-CA signed, so discovery and the JWKS fallback both fail and oauth2-proxy exits "error building verifiers" → crash loop on both replicas, human OIDC login included → add `SSL_CERT_FILE: "/etc/ssl/combined/ca-certificates.crt"` to the configmap (the combined bundle is already mounted). - apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — blocking: OAUTH2_PROXY_ALLOWED_GROUPS=akP-vlogs-admin is still enforced on bearer sessions (provider.Authorize), with groups read from the `ak_groups` claim. A Vault identity token has no such claim unless the terraform-vault #179 role template emits `ak_groups: ["akP-vlogs-admin"]` → confirm #179 sets it, otherwise every Vault JWT gets 403. - apps/base/vlogs/oauth2-proxy-configmap.yaml:29 — nit: startup now hard-depends on Vault being reachable (verifier build fails the pod if Vault is down) → accept explicitly or note in the PR body.
benvin merged commit e63b85d5a5 into main 2026-11-16 21:30:40 +11:00
benvin deleted branch benvin/vlogs-vault-jwt 2026-11-16 21:30:40 +11:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#587