165 lines
6 KiB
YAML
165 lines
6 KiB
YAML
|
|
---
|
||
|
|
# Loki data backup via restic to Hetzner Object Storage (DEV-485,
|
||
|
|
# DEV-482 Option 4). Step 2 of the Option 4 rollout.
|
||
|
|
#
|
||
|
|
# Streams the RWO PVC `loki-storage-encrypted` (mounted read-only)
|
||
|
|
# into `s3:${S3_ENDPOINT}/${S3_BUCKET}/restic/loki`, a client-side
|
||
|
|
# encrypted restic repository. Deployed in parallel with the legacy
|
||
|
|
# `backup-volumes` CronJob — do not retire that job until DEV-482
|
||
|
|
# step 6 (restore drill passed).
|
||
|
|
#
|
||
|
|
# podAffinity co-schedules with the Loki pod (app=loki, topology
|
||
|
|
# kubernetes.io/hostname). RWO permits additional read-only mounts
|
||
|
|
# on the node that holds the PVC's VolumeAttachment, so this
|
||
|
|
# survives Loki being rescheduled to a different worker.
|
||
|
|
apiVersion: batch/v1
|
||
|
|
kind: CronJob
|
||
|
|
metadata:
|
||
|
|
name: backup-loki-restic
|
||
|
|
namespace: monitoring
|
||
|
|
labels:
|
||
|
|
app: backup
|
||
|
|
type: loki
|
||
|
|
backend: restic
|
||
|
|
spec:
|
||
|
|
schedule: "0 3 * * *"
|
||
|
|
concurrencyPolicy: Forbid
|
||
|
|
successfulJobsHistoryLimit: 3
|
||
|
|
failedJobsHistoryLimit: 3
|
||
|
|
jobTemplate:
|
||
|
|
metadata:
|
||
|
|
labels:
|
||
|
|
app: backup
|
||
|
|
type: loki
|
||
|
|
backend: restic
|
||
|
|
spec:
|
||
|
|
backoffLimit: 2
|
||
|
|
activeDeadlineSeconds: 3600
|
||
|
|
template:
|
||
|
|
metadata:
|
||
|
|
labels:
|
||
|
|
app: backup
|
||
|
|
type: loki
|
||
|
|
backend: restic
|
||
|
|
spec:
|
||
|
|
restartPolicy: OnFailure
|
||
|
|
affinity:
|
||
|
|
podAffinity:
|
||
|
|
requiredDuringSchedulingIgnoredDuringExecution:
|
||
|
|
- labelSelector:
|
||
|
|
matchExpressions:
|
||
|
|
- key: app
|
||
|
|
operator: In
|
||
|
|
values:
|
||
|
|
- loki
|
||
|
|
topologyKey: kubernetes.io/hostname
|
||
|
|
containers:
|
||
|
|
- name: restic
|
||
|
|
image: restic/restic:0.17.3
|
||
|
|
env:
|
||
|
|
- name: AWS_ACCESS_KEY_ID
|
||
|
|
valueFrom:
|
||
|
|
secretKeyRef:
|
||
|
|
name: monitoring-s3-backup
|
||
|
|
key: access-key
|
||
|
|
- name: AWS_SECRET_ACCESS_KEY
|
||
|
|
valueFrom:
|
||
|
|
secretKeyRef:
|
||
|
|
name: monitoring-s3-backup
|
||
|
|
key: secret-key
|
||
|
|
- name: RESTIC_PASSWORD
|
||
|
|
valueFrom:
|
||
|
|
secretKeyRef:
|
||
|
|
name: monitoring-s3-backup
|
||
|
|
key: restic-password
|
||
|
|
- name: S3_ENDPOINT
|
||
|
|
valueFrom:
|
||
|
|
secretKeyRef:
|
||
|
|
name: monitoring-s3-backup
|
||
|
|
key: endpoint
|
||
|
|
- name: S3_BUCKET
|
||
|
|
valueFrom:
|
||
|
|
secretKeyRef:
|
||
|
|
name: monitoring-s3-backup
|
||
|
|
key: bucket
|
||
|
|
- name: RESTIC_REPOSITORY
|
||
|
|
value: "s3:$(S3_ENDPOINT)/$(S3_BUCKET)/restic/loki"
|
||
|
|
command:
|
||
|
|
- /bin/sh
|
||
|
|
- -c
|
||
|
|
- |
|
||
|
|
set -eu
|
||
|
|
echo "=== backup-loki-restic started at $(date -u +%FT%TZ) ==="
|
||
|
|
echo "Repository: ${RESTIC_REPOSITORY}"
|
||
|
|
|
||
|
|
# First-run tolerance: init if the repo isn't there yet.
|
||
|
|
# `restic cat config` is the tightest existence probe; use
|
||
|
|
# `snapshots` per plan spec — either exits 0 iff the repo
|
||
|
|
# is initialised.
|
||
|
|
if restic snapshots >/dev/null 2>&1; then
|
||
|
|
echo "Repo exists, skipping init."
|
||
|
|
else
|
||
|
|
echo "Repo missing, initialising..."
|
||
|
|
restic init
|
||
|
|
fi
|
||
|
|
|
||
|
|
echo "--- restic backup /source ---"
|
||
|
|
restic backup /source \
|
||
|
|
--tag loki \
|
||
|
|
--host k3s \
|
||
|
|
--exclude '*.tmp'
|
||
|
|
|
||
|
|
echo "--- restic forget/prune ---"
|
||
|
|
restic forget --tag loki \
|
||
|
|
--keep-daily 7 \
|
||
|
|
--keep-weekly 4 \
|
||
|
|
--keep-monthly 6 \
|
||
|
|
--prune
|
||
|
|
|
||
|
|
echo "--- restic check --read-data-subset=5% ---"
|
||
|
|
CHECK_STATUS=0
|
||
|
|
restic check --read-data-subset=5% || CHECK_STATUS=$?
|
||
|
|
echo "restic check exit: ${CHECK_STATUS}"
|
||
|
|
|
||
|
|
# Textfile-collector metrics. Written into an emptyDir per
|
||
|
|
# the current pattern used by backup-volumes and
|
||
|
|
# backup-k8s-resources. Once a node-exporter textfile
|
||
|
|
# collector path is wired up, these become scrapeable —
|
||
|
|
# see the follow-up notes in DEV-482.
|
||
|
|
{
|
||
|
|
echo "backup_loki_success $([ ${CHECK_STATUS} -eq 0 ] && echo 1 || echo 0)"
|
||
|
|
echo "backup_loki_timestamp_seconds $(date +%s)"
|
||
|
|
echo "backup_loki_check_status ${CHECK_STATUS}"
|
||
|
|
} > /metrics/backup_loki.prom
|
||
|
|
|
||
|
|
echo "=== backup-loki-restic finished at $(date -u +%FT%TZ) ==="
|
||
|
|
exit ${CHECK_STATUS}
|
||
|
|
volumeMounts:
|
||
|
|
- name: loki-data
|
||
|
|
mountPath: /source
|
||
|
|
readOnly: true
|
||
|
|
- name: metrics
|
||
|
|
mountPath: /metrics
|
||
|
|
- name: cache
|
||
|
|
mountPath: /root/.cache/restic
|
||
|
|
resources:
|
||
|
|
# Requests deliberately lowered from the plan doc's
|
||
|
|
# 200m/256Mi — worker-2 (Loki node) has ~150m free CPU
|
||
|
|
# and podAffinity forces us onto it. 100m/128Mi mirrors
|
||
|
|
# the sibling backup CronJobs; limits stay generous so
|
||
|
|
# restic can burst during pack/check.
|
||
|
|
requests:
|
||
|
|
cpu: 100m
|
||
|
|
memory: 128Mi
|
||
|
|
limits:
|
||
|
|
cpu: 1500m
|
||
|
|
memory: 1Gi
|
||
|
|
volumes:
|
||
|
|
- name: loki-data
|
||
|
|
persistentVolumeClaim:
|
||
|
|
claimName: loki-storage-encrypted
|
||
|
|
- name: metrics
|
||
|
|
emptyDir: {}
|
||
|
|
- name: cache
|
||
|
|
emptyDir: {}
|