Point issue-core ArgoCD Application at Forgejo Git source
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.
This commit is contained in:
parent
c3e1525821
commit
60447e8b0a
3 changed files with 3 additions and 2 deletions
|
|
@ -10,6 +10,7 @@ spec:
|
|||
description: Guardrails for Railiance tenant applications deployed by ArgoCD.
|
||||
sourceRepos:
|
||||
- https://gitea.coulomb.social/coulomb/*.git
|
||||
- https://forgejo.coulomb.social/coulomb/*.git
|
||||
destinations:
|
||||
- server: https://kubernetes.default.svc
|
||||
namespace: "*"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue