tegwick
60447e8b0a
ArgoCD was still tracking gitea.coulomb.social, which lags Forgejo after the registry migration. Sync issue-core workload manifests from forgejo.coulomb.social so backend ConfigMap updates land on CoulombCore. Also allow forgejo.coulomb.social in railiance-tenants AppProject sourceRepos.
27 lines
662 B
YAML
27 lines
662 B
YAML
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: issue-core
|
|
namespace: argocd
|
|
labels:
|
|
app.kubernetes.io/part-of: railiance-gitops
|
|
railiance.io/domain: issue-core
|
|
annotations:
|
|
argocd.argoproj.io/sync-wave: "10"
|
|
spec:
|
|
project: railiance-tenants
|
|
source:
|
|
repoURL: https://forgejo.coulomb.social/coulomb/issue-core.git
|
|
targetRevision: main
|
|
path: k8s/railiance
|
|
destination:
|
|
server: https://kubernetes.default.svc
|
|
namespace: issue-core
|
|
syncPolicy:
|
|
automated:
|
|
prune: true
|
|
selfHeal: true
|
|
syncOptions:
|
|
- CreateNamespace=true
|
|
- ApplyOutOfSyncOnly=true
|
|
- PruneLast=true
|