From a57c459c8a407b1af4f7d339fcb2a887d6b7822a Mon Sep 17 00:00:00 2001
From: juvdiaz <juvenal.diaz@oracle.com>
Date: Mon, 29 Jun 2026 21:02:11 -0600
Subject: [PATCH] Archive legacy ARR Kubernetes manifests

---
 README.md                                           | 6 +++---
 README.md.tmpl                                      | 6 +++---
 {apps => archive/apps}/arr-stack/ingress.yaml       | 0
 {apps => archive/apps}/arr-stack/kustomization.yaml | 0
 {apps => archive/apps}/arr-stack/namespace.yaml     | 0
 {apps => archive/apps}/arr-stack/storage.yaml       | 0
 {apps => archive/apps}/arr-stack/web-app.yaml       | 0
 7 files changed, 6 insertions(+), 6 deletions(-)
 rename {apps => archive/apps}/arr-stack/ingress.yaml (100%)
 rename {apps => archive/apps}/arr-stack/kustomization.yaml (100%)
 rename {apps => archive/apps}/arr-stack/namespace.yaml (100%)
 rename {apps => archive/apps}/arr-stack/storage.yaml (100%)
 rename {apps => archive/apps}/arr-stack/web-app.yaml (100%)

diff --git a/README.md b/README.md
index c5aaa7b..6b902d0 100644
--- a/README.md
+++ b/README.md
@@ -833,10 +833,10 @@ The ARR/media stack is intentionally not deployed by the Kubernetes app
 pipeline. It is better suited to a Docker Compose stack on the Debian host with
 persistent volumes under `/data`, where large media paths, qBittorrent writes,
 and service config directories can survive cluster rebuilds without OpenEBS
-node-affinity or PVC migration concerns. The legacy `apps/arr-stack` manifests
-are retained only as migration reference. The active host-level Compose
+node-affinity or PVC migration concerns. The active host-level Compose
 definition lives under `infra/arr-stack` and stores persistent data under
-`/data/arr`.
+`/data/arr`. Historical Kubernetes manifests are archived under
+`archive/apps/arr-stack` for migration reference only.
 
 ## Storage
 
diff --git a/README.md.tmpl b/README.md.tmpl
index 232de02..f587757 100644
--- a/README.md.tmpl
+++ b/README.md.tmpl
@@ -833,10 +833,10 @@ The ARR/media stack is intentionally not deployed by the Kubernetes app
 pipeline. It is better suited to a Docker Compose stack on the Debian host with
 persistent volumes under `/data`, where large media paths, qBittorrent writes,
 and service config directories can survive cluster rebuilds without OpenEBS
-node-affinity or PVC migration concerns. The legacy `apps/arr-stack` manifests
-are retained only as migration reference. The active host-level Compose
+node-affinity or PVC migration concerns. The active host-level Compose
 definition lives under `infra/arr-stack` and stores persistent data under
-`/data/arr`.
+`/data/arr`. Historical Kubernetes manifests are archived under
+`archive/apps/arr-stack` for migration reference only.
 
 ## Storage
 
diff --git a/apps/arr-stack/ingress.yaml b/archive/apps/arr-stack/ingress.yaml
similarity index 100%
rename from apps/arr-stack/ingress.yaml
rename to archive/apps/arr-stack/ingress.yaml
diff --git a/apps/arr-stack/kustomization.yaml b/archive/apps/arr-stack/kustomization.yaml
similarity index 100%
rename from apps/arr-stack/kustomization.yaml
rename to archive/apps/arr-stack/kustomization.yaml
diff --git a/apps/arr-stack/namespace.yaml b/archive/apps/arr-stack/namespace.yaml
similarity index 100%
rename from apps/arr-stack/namespace.yaml
rename to archive/apps/arr-stack/namespace.yaml
diff --git a/apps/arr-stack/storage.yaml b/archive/apps/arr-stack/storage.yaml
similarity index 100%
rename from apps/arr-stack/storage.yaml
rename to archive/apps/arr-stack/storage.yaml
diff --git a/apps/arr-stack/web-app.yaml b/archive/apps/arr-stack/web-app.yaml
similarity index 100%
rename from apps/arr-stack/web-app.yaml
rename to archive/apps/arr-stack/web-app.yaml