- Notifications via generic webhook to the Telegram Bot API: the engine's
native telegram service only supports channels and negative group IDs,
so a positive private chat_id never worked ("chat not found").
- Only on-sync-failed and on-health-degraded triggers; on-sync-succeeded
dropped (CI already reports successful deploys).
- Subscribe annotations on polymarket-bot, researchowl and n8n.
- prune: true on polymarket-bot, guarded by Prune=false on the postgres
PVC so removing the manifest from git can never destroy the data.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
26 lines
758 B
YAML
26 lines
758 B
YAML
apiVersion: v1
|
|
kind: PersistentVolumeClaim
|
|
metadata:
|
|
annotations:
|
|
# Never let ArgoCD prune this PVC: it holds the paper-trading postgres data.
|
|
argocd.argoproj.io/sync-options: Prune=false
|
|
pv.kubernetes.io/bind-completed: 'yes'
|
|
pv.kubernetes.io/bound-by-controller: 'yes'
|
|
volume.beta.kubernetes.io/storage-provisioner: rancher.io/local-path
|
|
volume.kubernetes.io/selected-node: chemavx-k8
|
|
volume.kubernetes.io/storage-provisioner: rancher.io/local-path
|
|
labels:
|
|
app: postgres
|
|
name: data-postgres-0
|
|
namespace: polymarket-bot
|
|
spec:
|
|
accessModes:
|
|
- ReadWriteOnce
|
|
resources:
|
|
requests:
|
|
storage: 5Gi
|
|
storageClassName: local-path
|
|
volumeMode: Filesystem
|
|
volumeName: pvc-327bbc6d-dcc6-46b4-9d78-db950f71eb98
|
|
|