fix: retire obsolete Authentik Redis in operator 0.1.4 #3
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
homelab/authentik-operator!3
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/image-update-coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Authentik2025.10+ no longer uses Redis; current supported/deployed2026.8.x remains on the same image. Removes generation and obsolete environment/readiness state. Reconciliation deletes only owned Redis Deployment/Service using UID/resourceVersion preconditions and preserves foreign resources. Stateful PostgreSQL/bootstrap configuration unchanged. Deterministic ownership/credential regressions and full unit/integration suite passed; isolated E2E is running after resolving local Docker disk exhaustion using only this run’s temporary extraction image. Operator/chart release bumped0.1.4. Standard Renovate source maintenance and weekly Sunday03:15UTC cron enabled.
Verification update: full unit/envtest suite passed; owned/foreign/unowned Redis cleanup regressions passed; operator Helm lint passed; the actual multi-stage operator image built successfully. Local Kind E2E did not reach application specs because its cert-manager fixture timed out; host OOM events were observed, so the isolated Kind cluster was removed and no further workstation retries will be made. Production rollout will verify owned Redis removal, unchanged bootstrap credential hash, server/worker readiness and OIDC discovery. The release is intentionally Authentik2025.10+ only, preserving the deployed2026.8.5 image.
Remote E2E verification now PASSED on the merged source84eed34: https://github.com/morten-olsen/homelab-authentik-operator/actions/runs/40414517566 (8m4s). Local unit/envtest/ownership regressions passed as recorded. Waiting on existing multiarchitecture release publication before updating the core operator pin.
Operator0.1.4 image and Helm chart are now published through the existing release workflow. helm show/template resolved the0.1.4 package and expected ghcr.io/morten-olsen/homelab-authentik-operator:0.1.4 image. Server-side dry-run in authentik namespace passed. Core adoption PR homelab/core#78 passed CI and is merged; GitOps rollout verification is in progress.
Deployed core1c069fb2d8a53895be1e973d50d79d40c45208b8 and published operator0.1.4. Owned obsolete Redis Deployment/Service are absent; server/worker no longer contain AUTHENTIK_REDIS__HOST and the stale RedisReady condition is removed. Both applications remain ready on Authentik2026.8.5. Bootstrap credential hash exactly matches the pre-rollout baseline. All eight affected ArgoCD Applications are Synced/Healthy. Authentik readiness and NetBird OIDC discovery return200; browser follows NetBird SSO to the rendered Authentik login form with no page errors. Full authenticated user login was not performed. Both Dawarich/Immich cache pods retain their original UIDs; VPN management/signal connected. Temporary Kind, namespace/PV, test applications and helper pods were removed; temporary local source/render artifacts cleaned.