fix: staging uses namespace default, not foursat

.gitea/workflows/kub-deploy.yml

@@ -92,10 +92,9 @@ jobs:
           
           # Apply manifests and restart
           sshpass -e ssh -o StrictHostKeyChecking=no root@${{ env.K8S_SERVER }} "
-            kubectl create namespace foursat --dry-run=client -o yaml | kubectl apply -f - &&
             kubectl apply -f /tmp/cms-deployment.yaml &&
-            kubectl rollout restart deployment/cms -n foursat &&
+            kubectl rollout restart deployment/cms &&
-            kubectl rollout status deployment/cms -n foursat --timeout=180s &&
+            kubectl rollout status deployment/cms --timeout=180s &&
             rm -f /tmp/cms-deployment.yaml
           "
           echo "✅ Deployed!"

k8s/staging/cms-deployment.yaml

@@ -4,7 +4,7 @@ apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
   name: cms-uploads-pvc
-  namespace: foursat
+  namespace: default
   labels:
     app: cms
 spec:
@@ -20,7 +20,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: cms
-  namespace: foursat
+  namespace: default
   labels:
     app: cms
 spec:
@@ -116,7 +116,7 @@ apiVersion: v1
 kind: Service
 metadata:
   name: cms-svc
-  namespace: foursat
+  namespace: default
 spec:
   selector:
     app: cms
@@ -132,7 +132,7 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: cms-ingress
-  namespace: foursat
+  namespace: default
   annotations:
     kubernetes.io/ingress.class: "nginx"
     cert-manager.io/cluster-issuer: "letsencrypt-prod"