BackupPC is a high-performance, enterprise-grade system for backing up Linux, Windows and macOS PCs and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain.

$ helm repo add fermosit https://harbor.fermosit.es/chartrepo/library
$ helm install my-release fermosit/backuppc

This chart bootstraps a BackupPC deployment on a Kubernetes cluster using the Helm package manager.

This chart is based on another awesome chart by bitnami.

• Kubernetes 1.12+
• Helm 3.1.0
• PV provisioner support in the underlying infrastructure
• ReadWriteOnce volumes

To install the chart with the release name my-release:

helm install my-release fermosit/backuppc

The command deploys BackupPC on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

To uninstall/delete the my-release deployment:

helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

The above parameters map to the env variables defined in docker image environment vars. For more information please refer to the docker image documentation.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install my-release \
  --set backuppcWebUser=backuppc \
  --set backuppcWebPasswd=password \
  --set ingress.enabled=true \
  --set ingress.hostname=backuppc.127-0-0-1.nip.io \
  fermosit/backuppc

The above command sets the BackupPC administrator account username and password to backuppc and password respectively. Additionally, it creates a ingress to access app through http://backuppc.127-0-0-1.nip.io .

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install my-release -f values.yaml fermosit/backuppc

Tip: You can use the default values.yaml

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

This chart provides support for Ingress resources. If an Ingress controller, such as nginx-ingress or traefik, that Ingress controller can be used to serve WordPress.

To enable Ingress integration, set ingress.enabled to true. The ingress.hostname property can be used to set the host name. The ingress.tls parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host.

The chart also facilitates the creation of TLS secrets for use with the Ingress controller, with different options for certificate management.

The BackupPC image image stores the BackupPC data and configurations at the /etc/backuppc, /home/backuppc and /data/backuppc paths of the container. Persistent Volume Claim is used to keep the data across deployments.

If you encounter errors when working with persistent volumes, refer to our troubleshooting guide for persistent volumes.

In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the extraEnvVars property.

backuppc:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

Alternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the extraEnvVarsCM or the extraEnvVarsSecret values.

If additional containers are needed in the same pod as WordPress (such as additional metrics or logging exporters), they can be defined using the sidecars parameter. If these sidecars export extra ports, extra port definitions can be added using the service.extraPorts parameter. Learn more about configuring and using sidecar containers.

This chart allows you to set your custom affinity using the affinity parameter. Find more information about Pod affinity in the kubernetes documentation.

As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters.