Bring your own database

Many Helm charts and other deployments typically provide a method to co-deploy the required databases.

Redundancy

Kubernetes is different to a typical virtual machine setup. While virtual machines may be live migrated when the underlying hardware is put into maintenance, in Kubernetes node maintenance means individual pods will be stopped and restarted on a different node. In other words, database setups in Kubernetes must be redundant. This also means that the individual database instances need to replicate the data themselves, ARISnet does not automatically replicate the data between the individual database pods.

Monitoring

Simply starting a database pod does not automatically create monitoring for your database. Please take a look at the OpenShift Monitoring documentation on setting up monitoring for your database.

Backups

You can create a backup on an S3 bucket. You can request an S3 bucket yourself with the following YAML:

---
apiVersion: appcat.vshn.io/v1
kind: ObjectBucket
metadata:
   name: <project>-s3-bucket-pgbackup
   namespace: aris-<project>
spec:
   parameters:
     bucketName: <project>-s3-bucket-pgbackup
     region: at-vie-2
   writeConnectionSecretToRef:
     name: <project>-s3-bucket-pgbackup

Note

Please do not use at-vie-1 as this is the zone where the cluster is running in.