This is an example project to show that you can run a Bareos Filedaemon as a Sidecar in a Kubernetes deployment to do logical backup and restore of the application you have deployed. The example will deploy a Wordpress blog with a MySQL database backend.
While this repository is meant as a reference to see how this can be achieved, we provide steps to reproduce the setup. However, this is by no means ready to be used in production.
You will have two deployments: one for the MySQL database and one for the Wordpress blog. The POD for Wordpress will have a sidecar container that runs the Bareos Filedaemon. That sidecar is configured to have access to the same persistent volume as the Wordpress container, so it can backup and restore the volume's contents. The sidecar container will also have the MySQL database credentials configured so it can access the MySQL database for backup and restore.
In the directory container-image you'll find a Dockerfile to build a container image that will run bareos-fd.
The image can be customized using environment variables at deployment time. This will configure the bareos filedaemon and the mysql client in the resulting container.
The directory k8s is a kubernetes kustomization directory that you can use to deploy the application with its bareos-fd sidecar. Before deploying you will need to change DIR_ADDRESS in wordpress.yaml to point to your director.
In the directory bareos-dir.d you will find example configuration for your director to back up and restore the Wordpress blog.