- k3s 정기 점검 중 outline-data 볼륨 스냅샷 256개(하드캡 250 초과)로
critical-snapshot/critical-backup 신규 생성 실패 발견
- kubectl delete(webhook이 finalizer 유지)와 파드 재배포/재attach
둘 다 무효였음을 확인 후, Longhorn REST API snapshotPurge 반복 호출로
256 -> 58개 정상화
- 근본 원인(retain 정책이 왜 이 볼륨만 실패했는지)은 미확정으로 남김
Switched Bunny iron-kr-nowaf origin from :443 (Traefik) to :9443 (APISIX,
no SafeLine plugin) since APISIX plugins are per-route. Used existing
:9443 path (juiceshop already there) instead of opening a new OpenWrt
port. Outline route managed via ApisixTls + ApisixRoute CRDs because
admin-API direct PUTs get swept by apisix-ingress-controller as orphans.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Created new Bunny pull zone iron-kr-nowaf (ID 5720695) without Shield to
host outline.inouter.com exclusively. Uploaded *.inouter.com wildcard cert
from cert-manager since Bunny LE auto-provision kept returning invalid.
Restored 7 CRS rules (942100,932230/235/260/370/380,933160) on iron-kr
Shield so vault/n8n/telegram-webhook/jarvis regain protection.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
