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.
21 lines
611 B
Text
21 lines
611 B
Text
# Copy to issue-core.repository.sops.yaml, fill from the approved
|
|
# operator/OpenBao path, then encrypt with:
|
|
# sops -e -i argocd/repositories/issue-core.repository.sops.yaml
|
|
#
|
|
# Do not commit plaintext credentials.
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: issue-core-repository
|
|
namespace: argocd
|
|
labels:
|
|
argocd.argoproj.io/secret-type: repository
|
|
app.kubernetes.io/part-of: railiance-gitops
|
|
railiance-platform/component: gitops
|
|
stringData:
|
|
type: git
|
|
project: railiance-tenants
|
|
url: https://forgejo.coulomb.social/coulomb/issue-core.git
|
|
username: CHANGE_ME
|
|
password: CHANGE_ME
|
|
|