funman300
6905f26b56
Build and Deploy / build-and-push (push) Successful in 35s
Secrets committed in prior commits (matomo-secret.yaml, secret-analytics-auth.yaml) have been scrubbed from history via filter-branch — rotate those credentials immediately. Going forward: - deploy/*-secret.yaml is gitignored; apply manually with kubectl - deploy/matomo-secret.yaml.example shows the required shape - ArgoCD ignoreDifferences on matomo-secret prevents it pruning a manually-applied secret - Remove matomo-secret.yaml from kustomization.yaml so ArgoCD never manages it again Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
29 lines
659 B
YAML
29 lines
659 B
YAML
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: solitaire-server
|
|
namespace: argocd
|
|
spec:
|
|
project: default
|
|
source:
|
|
repoURL: https://git.aleshym.co/funman300/Rusty_Solitare.git
|
|
targetRevision: master
|
|
path: deploy
|
|
destination:
|
|
server: https://kubernetes.default.svc
|
|
namespace: solitaire
|
|
# Secrets are applied manually and must not be pruned by ArgoCD.
|
|
ignoreDifferences:
|
|
- group: ""
|
|
kind: Secret
|
|
name: matomo-secret
|
|
namespace: solitaire
|
|
jsonPointers:
|
|
- /data
|
|
syncPolicy:
|
|
automated:
|
|
prune: true
|
|
selfHeal: true
|
|
syncOptions:
|
|
- CreateNamespace=true
|