wordpress

This commit is contained in:
2025-08-25 19:03:30 +02:00
parent 9287bdb494
commit 643fb44795
7 changed files with 39 additions and 193 deletions

BIN
bookstack/.DS_Store vendored Normal file

Binary file not shown.

BIN
wordpress/.DS_Store vendored Normal file

Binary file not shown.

View File

@@ -1,140 +1,90 @@
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-csi-hourly
name: wordpress-csi-hourly
namespace: velero
labels:
velero.io/storage-location: ceph-bucket
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 15-22 * * * # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "0 15-22 * * *"
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: ["wordpress"]
ttl: 8h
snapshotVolumes: true
defaultVolumesToFsBackup: false
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: ceph-bucket
ttl: 8h0m0s
csiSnapshotTimeout: 10m
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-csi-daily
name: wordpress-csi-daily
namespace: velero
labels:
velero.io/storage-location: ceph-bucket
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 0 * * * # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "0 0 * * *"
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: ["wordpress"]
ttl: 168h
snapshotVolumes: true
defaultVolumesToFsBackup: false
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: ceph-bucket
ttl: 168h0m0s
csiSnapshotTimeout: 10m
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-csi-weekly
name: wordpress-csi-weekly
namespace: velero
labels:
velero.io/storage-location: ceph-bucket
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 0 * * 1 # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "0 0 * * 1"
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: ["wordpress"]
ttl: 730h
snapshotVolumes: true
defaultVolumesToFsBackup: false
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: ceph-bucket
ttl: 730h0m0s
csiSnapshotTimeout: 10m
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-restic-daily
name: wordpress-daily
namespace: velero
labels:
velero.io/storage-location: aux-balancer-minio
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 0 * * * # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "30 2 * * *" # tous les jours 02:30
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: [wordpress]
storageLocation: default
ttl: 336h # ~14 jours
snapshotVolumes: false
defaultVolumesToFsBackup: true
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: aux-balancer-minio
ttl: 168h0m0s
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-restic-weekly
name: wordpress-weekly
namespace: velero
labels:
velero.io/storage-location: aux-balancer-minio
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 0 * * 1 # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "0 3 * * 0" # chaque dimanche 03:00
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: [wordpress]
storageLocation: default
ttl: 1344h # ~8 semaines
snapshotVolumes: false
defaultVolumesToFsBackup: true
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: aux-balancer-minio
ttl: 730h0m0s
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: wordpress-backup-restic-monthly
name: wordpress-monthly
namespace: velero
labels:
velero.io/storage-location: aux-balancer-minio
spec:
# Schedule is a Cron expression defining when to run the Backup
schedule: 0 0 1 * * # every hour
# Specifies whether to use OwnerReferences on backups created by this Schedule.
# Notice: if set to true, when schedule is deleted, backups will be deleted too. Optional.
schedule: "0 4 1 * *" # 1er du mois 04:00
useOwnerReferencesInBackup: true
template:
csiSnapshotTimeout: 10m0s
includedNamespaces: [wordpress]
storageLocation: default
ttl: 8760h # ~12 mois
snapshotVolumes: false
defaultVolumesToFsBackup: true
hooks: {}
includedNamespaces:
- wordpress
metadata: {}
storageLocation: aux-balancer-minio
ttl: 4380h0m0s

View File

@@ -1,32 +1,3 @@
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: wordpress-db
# Change "rook-ceph" provisioner prefix to match the operator namespace if needed
provisioner: rook-ceph.cephfs.csi.ceph.com
parameters:
# clusterID is the namespace where the rook cluster is running
# If you change this namespace, also change the namespace below where the secret namespaces are defined
clusterID: rook-ceph
# CephFS filesystem name into which the volume shall be created
fsName: wordpress
# Ceph pool into which the volume shall be created
# Required for provisionVolume: "true"
pool: wordpress-replicated
# The secrets contain Ceph admin credentials. These are generated automatically by the operator
# in the same namespace as the cluster.
csi.storage.k8s.io/provisioner-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph
csi.storage.k8s.io/controller-expand-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph
csi.storage.k8s.io/node-stage-secret-name: rook-csi-cephfs-node
csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph
reclaimPolicy: Delete
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
@@ -38,7 +9,7 @@ spec:
resources:
requests:
storage: 4Gi
storageClassName: wordpress-db
storageClassName: cephfs-hyper
---
apiVersion: apps/v1
kind: Deployment
@@ -129,35 +100,6 @@ spec:
sessionAffinity: None
type: ClusterIP
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: wordpress-db-backup
# Change "rook-ceph" provisioner prefix to match the operator namespace if needed
provisioner: rook-ceph.cephfs.csi.ceph.com
parameters:
# clusterID is the namespace where the rook cluster is running
# If you change this namespace, also change the namespace below where the secret namespaces are defined
clusterID: rook-ceph
# CephFS filesystem name into which the volume shall be created
fsName: wordpress
# Ceph pool into which the volume shall be created
# Required for provisionVolume: "true"
pool: wordpress-replicated
# The secrets contain Ceph admin credentials. These are generated automatically by the operator
# in the same namespace as the cluster.
csi.storage.k8s.io/provisioner-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph
csi.storage.k8s.io/controller-expand-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph
csi.storage.k8s.io/node-stage-secret-name: rook-csi-cephfs-node
csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph
reclaimPolicy: Delete
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
@@ -169,7 +111,7 @@ spec:
resources:
requests:
storage: 4Gi
storageClassName: wordpress-db-backup
storageClassName: cephfs-hyper
---
apiVersion: apps/v1
kind: Deployment

View File

@@ -1,17 +0,0 @@
apiVersion: ceph.rook.io/v1
kind: CephFilesystem
metadata:
name: wordpress
namespace: rook-ceph
spec:
metadataPool:
replicated:
size: 3
dataPools:
- name: replicated
replicated:
size: 3
preserveFilesystemOnDelete: false
metadataServer:
activeCount: 1
activeStandby: true

View File

@@ -10,10 +10,10 @@ metadata:
spec:
tls:
- hosts:
- wordpress.undercloud.cf
- wordpress.apps.undercloud.dev
secretName: wordpress-tls
rules:
- host: wordpress.undercloud.cf
- host: wordpress.apps.undercloud.dev
http:
paths:
- path: /

View File

@@ -1,32 +1,3 @@
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: wordpress
# Change "rook-ceph" provisioner prefix to match the operator namespace if needed
provisioner: rook-ceph.cephfs.csi.ceph.com
parameters:
# clusterID is the namespace where the rook cluster is running
# If you change this namespace, also change the namespace below where the secret namespaces are defined
clusterID: rook-ceph
# CephFS filesystem name into which the volume shall be created
fsName: wordpress
# Ceph pool into which the volume shall be created
# Required for provisionVolume: "true"
pool: wordpress-replicated
# The secrets contain Ceph admin credentials. These are generated automatically by the operator
# in the same namespace as the cluster.
csi.storage.k8s.io/provisioner-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph
csi.storage.k8s.io/controller-expand-secret-name: rook-csi-cephfs-provisioner
csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph
csi.storage.k8s.io/node-stage-secret-name: rook-csi-cephfs-node
csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph
reclaimPolicy: Delete
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
@@ -38,7 +9,7 @@ spec:
resources:
requests:
storage: 8Gi
storageClassName: wordpress
storageClassName: cephfs-hyper
---
apiVersion: apps/v1
kind: Deployment