remove planpal-staging env

planpalto-helm/argocd/apps/planpal-staging.yaml

@@ -1,26 +0,0 @@
-apiVersion: argoproj.io/v1alpha1
-kind: Application
-metadata:
-  name: planpal-staging
-  namespace: argocd
-  finalizers:
-    - resources-finalizer.argocd.argoproj.io
-spec:
-  project: default
-  source:
-    repoURL: http://gitea-http.gitea.svc.cluster.local:3000/planpal/ch4.git
-    targetRevision: HEAD
-    path: planpalto-helm
-    helm:
-      valueFiles:
-        - values.yaml
-        - values-staging.yaml
-  destination:
-    server: https://kubernetes.default.svc
-    namespace: planpal-staging
-  syncPolicy:
-    automated:
-      prune: true
-      selfHeal: true
-    syncOptions:
-      - CreateNamespace=true

planpalto-helm/values-staging.yaml

@@ -1,30 +0,0 @@
-# Staging overrides. Everything else inherits values.yaml.
-# Pinned explicitly (not left to release-name defaults) so the two envs
-# provably never share a namespace, ALB, or cluster-scoped store.
-namespace: planpal-staging
-
-image:
-  frontend:
-    tag: latest
-  backend:
-    tag: latest
-
-externalSecrets:
-  storeName: staging-aws-planpal
-  # ponytail: staging points at the SAME planpal/* SM keys as prod for now.
-  # Give staging its own DB/config by pointing these at planpal-staging/* keys
-  # and letting the ESO role read them.
-  secrets:
-    backend-env: planpal/backend-env
-    aws-env: planpal/aws-env
-    seed-env: planpal/seed-env
-    frontend-env: planpal/frontend
-
-ingress:
-  host: staging.fakhri-k8.sandbox.devopsinstitute.id
-  certArn: arn:aws:acm:ap-southeast-3:134604498185:certificate/5d0f65f5-9d93-4c2e-87db-b9afe8972048
-  groupName: planpal-helm   # share the existing ALB; host differs so no collision
-
-# Seed the admin on staging too. Flip to false once seeded.
-seedJob:
-  enabled: true