Stash v1beta1 E2E test

[hossainemruz]

Workload Backup & Restore

• Deployment
  • General backup & restore
    • create Deployment
    • generate some sample data inside workload
    • create Storage Secret
    • create Repository
    • create BackupConfiguration
    • check if backup sidecar has been injected
    • wait for backup
    • check if repository status has been updated
    • check if check if respective BackupSession status has been updated
    • delete BackupConfiguration
    • wait for sidecar to be removed
    • delete sample data
    • create RestoreSession
    • check if init container has been added
    • wait for restore to to be complete
    • check if the workload has same sample data.
  • Leader Election
    • proceed up to backup of previous test(deployment will have multiple replica).
    • find leader pod and delete it.
    • check if new leader has been elected
    • check if backup is being taken as usual
  • Restore on different Deployment
    • proceed up to backup of first test
    • create another Deployment
    • create RestoreSession targeting second Deployment
    • check if backed up data from first Deployment has been restored in second Deployment.
• StatefulSet
  • General backup & restore
    • create StatefulSet with multiple replica & volumeClaimTemplate
    • generate sample data inside StatefulSet pods. (different data inside different pod)
    • create storage secret, Repository, BackupConfiguration
    • wait for backup. one BackupSession will create same number of snapshot as StatefulSet replica.
    • delete BackupConfiguration
    • delete sample data from StatefulSet pods
    • create RestoreSession
    • wait for restore to be completed
    • check if each pod's has same sample data that was created for this pod.
  • Restore on different StatefulSet
    • take backup similarly as previous test
    • create new StatefulSet similar to first one.
    • create RestoreSession targeting second StatefulSet.
    • wait for restore complete.
    • check if second StatefulSet's pod has similar data as respective first StatefulSet's pod.
  • Restore on Scaled Up StatefulSet
    • take backup as first test.
    • create second StatefulSet which has two more replica than first one.
    • configure RestoreSession rule to recover from first and second pods data of first SatetefulSet to the excess pods of second StatefulSet.
    • create RestoreSession and wait for restore to be completed.
    • check if first similar pods of second StatefulSet has same data as respective pods of first StatefulSet.
    • check if extra two pod's of second StatefulSet has same data as first and second pod's of first StatefulSet respectively.
• DaemonSet
  • General backup & restore
  • Restore on different DaemonSet
• ReplicaSet
  • same as Deployment
• ReplicationController
  • same as Deployment

Volume Backup & Restore

• General backup & restore
  • create a PVC
  • create a job with this PVC and generate sample data
  • create secret,Repository,BackupConfiguration
  • wait for backup complete
  • delete BackupConfiguration
  • create a job with the pvc and clear sample data
  • create RestoreSession targeting the pvc.
  • wait for restore complete
  • create a sample pod with recovered volume and check if sample data restored.
• Restore on different PVC

Database Backup & Restore

• Databases deployed with KubeDB
  • PostgreSQL
  • MySQL
  • MongoDB
  • ElasticSearch
• Databases deployed manually or other other operators
  • PostgreSQL
  • MySQL
  • MongoDB
  • ElasticSearch

Cluster Backup

• Backup Cluster YAMLs

Advance Use Cases

• Instant backup
  • create BackupConfiguration with large schedule
  • crate BackupSession crd targeting the BackupConfiguration
  • check if backup succeed
• Restore in different namespace
  • copy Repository, storage secret in target namespace
  • restore and check restored data

Webhook Test

• BackupConfiguration validator
• RestoreSesion validator

Default Backup Test

• Default backup deployment
• Default backup pvc
• Default backup database

Backend Test

• GCS
• AWS S3
• Minio
  • without tls
  • with tls
• Azure
• Swift
• B2
• Local
  • PVC
  • NFS

Metrics Test

• Check backup metrics
  • Success metrics
  • Failure metrics
• Check restore metrics
  • Success metrics
  • Failure metrics

[hossainemruz]

Respective items is being tracked in Zoho backlog