Skip to content

fix(authelia): remove orphaned PVC causing Progressing health#272

Merged
swares merged 3 commits into
mainfrom
docs/doc-corrections
Jul 22, 2026
Merged

fix(authelia): remove orphaned PVC causing Progressing health#272
swares merged 3 commits into
mainfrom
docs/doc-corrections

Conversation

@swares

@swares swares commented Jul 22, 2026

Copy link
Copy Markdown
Owner

The authelia-data PVC defined in pvc.yaml is never mounted by the Authelia Deployment. With local-path StorageClass (WaitForFirstConsumer), it stays Pending indefinitely. ArgoCD evaluates the PVC health as Progressing and rolls that up to the app, which has been stuck showing Progressing for 3+ days.

Fix: delete the manifest. ArgoCD prune will remove the PVC on next sync.

Risk: none — PVC was never bound, contains no data.

swares added 3 commits July 22, 2026 02:31
- CLAUDE.md: clarify RPi 4B / opi-zero2w-1 DNS roles
- ARCHITECTURE.md: add Reloader and Zot to services table
- HARDWARE.md: fix OPi Zero 2W #4 role (MQTT secondary broker)
- WORKFLOWS.md: note that standard workloads don't need gitops/apps/ entry
- services.md: add Reloader and Zot entries
- STANDUP.md: remove Proxmox API token ref; archive Phase 5
- LAB-DESIGN.md: add design-proposal disclaimer (Proxmox not implemented)
The PVC was never mounted by the Deployment (only config and secrets
volumes are used). It has been Pending for 3 days as local-path waits
for a consumer that never arrives, causing ArgoCD to report the app as
Progressing indefinitely.

No data loss risk: the PVC was never bound.
@swares
swares merged commit 63dd079 into main Jul 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant