Removing the exclusion caused the root app to apply argocd raw manifests directly (bypassing kustomize), breaking namespace resolution. The correct self-management design is: app-argocd.yaml Application is picked up by the root app, which then delegates to the argocd Application managing apps/argocd/ via kustomize. The exclusion of argocd/** prevents double-applying resources. Co-Authored-By: Paperclip <noreply@paperclip.ing>
22 lines
536 B
YAML
22 lines
536 B
YAML
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: stack-basicstack-de
|
|
namespace: argocd
|
|
spec:
|
|
project: default
|
|
source:
|
|
repoURL: git@forgejo.forgejo.svc.cluster.local:basicstack/stack.basicstack.de.git
|
|
targetRevision: main
|
|
path: apps
|
|
directory:
|
|
recurse: true
|
|
exclude: 'argocd/**'
|
|
destination:
|
|
server: https://kubernetes.default.svc
|
|
syncPolicy:
|
|
automated:
|
|
prune: false # Manual approval for deletions
|
|
selfHeal: true
|
|
syncOptions:
|
|
- CreateNamespace=true
|