Erich Blume 71cb256527 Deploy Authentik identity provider (C2 Mikado) (#227 )

## Summary
C2 Mikado chain for deploying Authentik as the SSO identity provider, replacing Dex.

This PR will evolve over multiple sessions. Each iteration adds documentation (prerequisite cards) and eventually code as leaf nodes are resolved.

## Current Mikado State
- **Goal:** `deploy-authentik` (active)
- **Leaf prerequisites:**
  - `build-authentik-container` — Build Nix container image
  - `provision-authentik-database` — Create PostgreSQL database on CNPG cluster
  - `create-authentik-secrets` — Create 1Password item with credentials

## Process refinements
- Updated agent-change-process with lessons from first attempt: reset code before committing cards, open PRs early

## Test plan
- [ ] `mise run docs-mikado` shows correct dependency chain
- [ ] Leaf nodes can be worked independently
- [ ] Container builds on ringtail
- [ ] Authentik starts and reaches healthy state
- [ ] Forgejo OAuth2 connector works

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/227

2026-02-20 12:55:59 -08:00

597 B

Raw Blame History

title

modified

last-reviewed

Explanation

Understanding-oriented content explaining the "why" behind BlumeOps design decisions.

Philosophy

Article	Description
why-gitops	Why infrastructure-as-code and GitOps for a homelab

Design

Article	Description
architecture	How all the pieces fit together
federated-login	How SSO works across BlumeOps (Authentik)
security-model	Network security, secrets, and access control

597 B Raw Blame History

Explanation

Philosophy

Design

597 B

Raw Blame History