fix version

README.md

@@ -1,6 +1,14 @@
 # Backup-Zen
 Backup-Zen is a Database Backup Solution Using Helm
 
+[Github Repo](https://github.com/rezachalak/backup-zen)
+[Installation](https://github.com/rezachalak/backup-zen#using-helm)
+[Web Site](https://rezachalak.github.io/backup-zen/)
+[Documentation](https://artifacthub.io/packages/helm/bzen/backup-zen)
+<!-- [Mailing List]() -->
+[Bug Reports](https://github.com/rezachalak/backup-zen/issues)
+<!-- [Donate]() -->
+<!-- [Scripting API]() -->
 
 ## Main features
 - Deploy on K8s using Helm
@@ -40,13 +48,13 @@ To uninstall the chart:
 
 ### Change Log
 
-March 7th, 2023: [MongoDB backup](https://github.com/mrezachalak/db-backup/tree/main/mongo_backup) initial release
+March 7th, 2023: MongoDB backup eligibilty added
 
 April 23th, 2023: MongoDB some typo fixed and some improvements has made in variable naming
 
-April 23th, 2023:[MySQL backup](https://github.com/mrezachalak/db-backup/tree/main/mysql_backup) initial release
+April 23th, 2023:MySQL backup eligibilty added
 
-April 23th, 2023:[PostgreSQL backup](https://github.com/mrezachalak/db-backup/tree/main/pg_backup) initial release
+April 23th, 2023:PostgreSQL backup eligibilty added
 
 August 10th, 2023: Dockerfile of postgres backup-zen client added
 

charts/backup-zen/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 description: BackupZen is a solution for backing up and uploading various database types, leveraging the power of K8s cronjobs. 
 name: backup-zen
-version: 0.1.0
+version: 0.1.1
 appVersion: 1.0.0
 kubeVersion: ">= 1.20.0"

charts/backup-zen/values.yaml

@@ -31,7 +31,7 @@ global:
   failedTeamsURL: https://myorg.webhook.office.com/webhookb2/blob-blob-blob
 
 cronjob:
-  # image: mrezachalak/pg-backup-zen:12.1
+  # image: rezachalak/pg-backup-zen:1.0.0
   pullPolicy: Always
   imagePullSecrets: []
   restartPolicy: Never

default-values.yaml

@@ -0,0 +1,99 @@
+databaseType: MongoDB # Can be one of PostgreSQL, MySQL or MongoDB 
+hostname: mydb.rds.amazonaws.com
+port: 54325
+# Select one of these two types:
+# oneByOne: preparing databaseName, username and password for each database as an array in oneByOne.creds must be provided
+# OR
+# adminUser: admin user credentials in adminUser.username and adminUser.password must be provided
+# default is adminUser
+credentialType: oneByOne
+# credsSecretName is the name of the secret where the database credentials are stored (can be used instead of setting oneByOne.creds)
+# It must contain 
+#   username and password >>> if credentialType == adminUser
+#   creds.json >>> if credentialType == oneByOne 
+# credsSecretName: mycreds-secret
+
+global:
+  charset: 
+  namespace: db-backups
+  createNamespace: true
+  rotation: true
+  #### SETTINGS FOR ROTATED BACKUPS ####
+  rotation_config:
+  # Which day to take the weekly backup from (1-7 = Monday-Sunday)
+    dayOfWeekToKeep: 5
+  # Number of days to keep daily backups
+    daysToKeep: 7
+  # How many weeks to keep weekly backups
+    weeksToKeep: 5
+  teamsNotification: true
+  succeededTeamsURL: https://myorg.webhook.office.com/webhookb2/blob-blob-blob
+  failedTeamsURL: https://myorg.webhook.office.com/webhookb2/blob-blob-blob
+
+cronjob:
+  # image: rezachalak/pg-backup-zen:1.0.0
+  pullPolicy: Always
+  imagePullSecrets: []
+  restartPolicy: Never
+  resources:
+     requests:
+       cpu: 1
+       memory: "1Gi"
+     limits:
+       cpu: 2
+       memory: "2Gi"
+  schedule: "0 0 * * *"
+  failedJobsHistoryLimit: 3
+  successfulJobsHistoryLimit: 3
+  storage:
+    createPVC: true
+    PVCName: mydb-backup
+    storageClass: standard
+    accessMode: ReadWriteOnce
+    PVCSize: 20Gi
+
+adminUser:
+# Optional username to connect to database as.  Will default to "root" if none specified.
+  username: root
+  password: roOtP@$$
+# Provide adminUser.username and adminUser.password in or create a secret in the specified namespace containing username and password in it 
+  # backupCredsSecretName: mydb-backup-creds
+
+oneByOne:
+# credsSecretName is the name of the secret where the database credentials are stored (can be used instead of oneByOne.creds)
+# credsSecretName: mycreds-secret
+# This secret must contain: creds.json
+  # creds.json: 
+    # [
+    # {
+      # "database_name": "",
+      # "username": "",
+      # "password": ""
+    # },..
+    # ]
+  creds:
+    - database_name: db1
+      username: user1
+      password: password1
+    - database_name: db2
+      username: user2
+      password: password2
+
+##### SETTINGS FOR AWS S3 ####
+backupUpload:
+  active: true
+# Supported objectStorages are: MinIO and AWS_S3
+  objectStorageType: MinIO
+  # objectStorageSecretName is the name of the secret where the credentials of object storage is stored.
+  # objectStorageSecretName: s3-secret-name
+  AWS_S3:
+    AWS_ACCESS_KEY_ID: "access"
+    AWS_DEFAULT_REGION: "us-west-1"
+    AWS_SECRET_ACCESS_KEY: "secret"
+    BUCKET_NAME: "mybucket-backup-zen"
+  MINIO:
+    MINIO_ACCESS_KEY_ID: access-key
+    MINIO_URL: https://localhost
+    MINIO_SECRET_ACCESS_KEY: secret
+    BUCKET_NAME: backupzen-minio
+    OBJECT_NAME: c342jhc34gf