fix: gpg encrypt permission warning message, update Kubernetes deployment example

README.md

@@ -95,8 +95,9 @@ For Kubernetes, you don't need to run it in scheduled mode. You can deploy it as
 apiVersion: batch/v1
 kind: Job
 metadata:
-  name: backup
+  name: backup-job
 spec:
+  ttlSecondsAfterFinished: 100
   template:
     spec:
       containers:
@@ -109,38 +110,27 @@ spec:
           command:
             - /bin/sh
             - -c
-            - bkup
-            - backup
-            - --storage
-            - s3
+            - backup -d dbname
           resources:
             limits:
               memory: "128Mi"
               cpu: "500m"
           env:
-            - name: DB_PORT
-              value: "5432"
             - name: DB_HOST
-              value: ""
-            - name: DB_NAME
-              value: ""
+              value: "postgres"
             - name: DB_USERNAME
-              value: ""
-            # Please use secret!
+              value: "postgres"
             - name: DB_PASSWORD
-              value: ""
-            - name: AWS_S3_ENDPOINT
-              value: "https://s3.amazonaws.com"
-            - name: AWS_S3_BUCKET_NAME
-              value: "xxx"
-            - name: AWS_REGION
-              value: "us-west-2"
-            - name: AWS_ACCESS_KEY
-              value: "xxxx"
-            - name: AWS_SECRET_KEY
-              value: "xxxx"
-            - name: AWS_DISABLE_SSL
-              value: "false"
+              value: "password"
+          volumeMounts:
+            - mountPath: /backup
+              name: backup
+      volumes:
+        - name: backup
+          hostPath:
+            path: /home/toto/backup # directory location on host
+            type: Directory # this field is optional
+      restartPolicy: Never
 ```
 ## Available image registries