docs: update kubernetes deployment

This commit is contained in:
2024-08-28 20:27:27 +02:00
parent 3e60f18df1
commit 31145ff29b
5 changed files with 100 additions and 69 deletions

View File

@@ -107,8 +107,12 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- backup
- --storage
- s3
resources:
limits:
memory: "128Mi"
@@ -119,13 +123,24 @@ spec:
- name: DB_HOST
value: ""
- name: DB_NAME
value: "dbname"
value: ""
- name: DB_USERNAME
value: "postgres"
value: ""
# Please use secret!
- name: DB_PASSWORD
value: ""
restartPolicy: Never
- 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"
```
## Available image registries

View File

@@ -13,12 +13,13 @@
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: Postgres database backup
title: PostgreSQL Backup Docker container image
email: hi@jonaskaninda.com
description: >- # this means to ignore newlines until "baseurl:"
PostgreSQL Backup and Restore Docker container image. Backup database to AWS S3 storage or SSH remote server.
PostgreSQL Backup is a Docker container image that can be used to backup and restore Postgres database.
It supports local storage, AWS S3 or any S3 Alternatives for Object Storage, and SSH compatible storage.
baseurl: "" # the subpath of your site, e.g. /blog
baseurl: "https://jkaninda.github.io/mysql-bkup/" # the subpath of your site, e.g. /blog
url: "jkaninda.github.io/pg-bkup/" # the base hostname & protocol for your site, e.g. http://example.com
twitter_username: jonaskaninda
github_username: jkaninda

View File

@@ -28,6 +28,8 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- backup
- --storage
@@ -82,6 +84,8 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- backup
- --storage
@@ -138,6 +142,8 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- restore
- --storage
@@ -196,6 +202,8 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- backup
- --storage
@@ -262,6 +270,8 @@ spec:
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- /bin/sh
- -c
- bkup
- backup
- --storage

View File

@@ -84,8 +84,6 @@ spec:
value: "xxx"
- name: SSH_REMOTE_PATH
value: "/home/jkaninda/backups"
- name: AWS_ACCESS_KEY
value: "xxxx"
- name: SSH_IDENTIFY_FILE
value: "/tmp/id_ed25519"
restartPolicy: Never

View File

@@ -1,18 +1,28 @@
apiVersion: batch/v1
kind: CronJob
kind: Job
metadata:
name: bkup-job
name: backup
spec:
schedule: "* * * * *"
jobTemplate:
spec:
template:
spec:
containers:
- name: pg-bkup
image: jkaninda/pg-bkup:v1.2.1
# In production, it is advised to lock your image tag to a proper
# release version instead of using `latest`.
# Check https://github.com/jkaninda/pg-bkup/releases
# for a list of available releases.
image: jkaninda/pg-bkup
command:
- pg-bkup backup -s s3 --path /custom_path
- /bin/sh
- -c
- bkup
- backup
- --storage
- s3
resources:
limits:
memory: "128Mi"
cpu: "500m"
env:
- name: DB_PORT
value: "5432"
@@ -25,8 +35,6 @@ spec:
# Please use secret!
- name: DB_PASSWORD
value: ""
- name: ACCESS_KEY
value: ""
- name: AWS_S3_ENDPOINT
value: "https://s3.amazonaws.com"
- name: AWS_S3_BUCKET_NAME
@@ -39,4 +47,3 @@ spec:
value: "xxxx"
- name: AWS_DISABLE_SSL
value: "false"
restartPolicy: OnFailure