fix: production uses namespace default + remove foursat namespace references

.gitea/workflows/prod-deploy.yml

@@ -94,10 +94,9 @@ jobs:
           
           # Apply manifests and update image
           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 set image deployment/cms cms=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }} -n foursat &&
+            kubectl set image deployment/cms cms=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }} &&
-            kubectl rollout status deployment/cms -n foursat --timeout=300s &&
+            kubectl rollout status deployment/cms --timeout=300s &&
             rm -f /tmp/cms-deployment.yaml
           "
           echo "✅ Deployed to Production!"

k8s/production/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:
@@ -86,7 +86,7 @@ apiVersion: v1
 kind: Service
 metadata:
   name: cms-svc
-  namespace: foursat
+  namespace: default
 spec:
   selector:
     app: cms
@@ -102,7 +102,7 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: cms-ingress
-  namespace: foursat
+  namespace: default
   annotations:
     cert-manager.io/cluster-issuer: "letsencrypt-prod"
     nginx.ingress.kubernetes.io/ssl-redirect: "true"