chore(backstage): Added SA for backstage to ArgoCD

manifests/artemis/argocd/kustomization.yaml

@@ -8,6 +8,8 @@ resources:
   - github.com/argoproj/argo-cd/manifests/cluster-install?ref=v3.2.0
   - ingressRoute.yaml
   - certificate.yaml
+  - backstage-sa.yaml
+  - backstage-rbac.yaml
 
 patches:
   - target:
@@ -120,17 +122,6 @@ patches:
         kind: ClusterRole
         name: argocd-server
 
-  # Backstage ServiceAccount
-  - target:
-      kind: ServiceAccount
-      name: backstage-argocd
-    patch: |-
-      apiVersion: v1
-      kind: ServiceAccount
-      metadata:
-        name: backstage-argocd
-        namespace: argocd
-
   # Map Backstage SA to Argo CD role:admin (full Argo CD permissions)
   - target:
       kind: ConfigMap
@@ -150,22 +141,3 @@ patches:
           p, argocd_users, applications, get, *, allow
           # Backstage SA -> role:admin
           g, system:serviceaccount:argocd:backstage-argocd, role:admin
-
-  # Optional: bind Backstage SA to argocd-server ClusterRole for Kubernetes-level API verbs Argo CD server uses
-  # If you only need Argo CD RBAC, you can omit this block
-  - target:
-      kind: ClusterRoleBinding
-      name: backstage-argocd-server-access
-    patch: |-
-      apiVersion: rbac.authorization.k8s.io/v1
-      kind: ClusterRoleBinding
-      metadata:
-        name: backstage-argocd-server-access
-      subjects:
-        - kind: ServiceAccount
-          name: backstage-argocd
-          namespace: argocd
-      roleRef:
-        apiGroup: rbac.authorization.k8s.io
-        kind: ClusterRole
-        name: argocd-server