bacula-backup Proxy Pod Image Installation

CommunityEnterprise

For Kubernetes PVC Data backup functionality, the Bacula Enterprise Kubernetes Plugin requires a dedicated Bacula Backup Proxy Pod. This Pod is deployed using an image that is available in the bacula-enterprise-kubernetes-tools package.

You must install this image manually into the local Docker image registry service used by your Kubernetes cluster as a source for application images.

Installation of the image can be performed with the following example commands:

# cd /opt/bacula/lib
# docker load -i bacula-backup-<timestamp>.tar
# docker image tag bacula-backup:<timestamp> <registry>/bacula-backup:<timestamp>
# docker push <registry>/bacula-backup:<timestamp>

where <timestamp> is the image version shipped with above package and <registry> is the location of your Docker image registry service. The exact procedure depends on your Kubernetes cluster deployment, so verify the steps above before running the Docker commands.

You can use any registry service available to your cluster, public or private, e.g. gcr.io/.

Depending on your cluster configuration, it may be necessary to set the baculaimage=<name> plugin parameter (see section Backup and Restore Plugin Parameters for details) to define which repository and Container image to use. The default for this parameter is bacula-backup:<timestamp> which may not be correct for your deployment.

Another example where you must modify the Bacula Backup Proxy Pod Image is when your registry requires authentication. See Advanced Bacula Backup Proxy Pod Deployment for more details.