Chart version: 7.2.1
Api version: v2
App version: 4.3.0
qBittorrent is a cross-platform free and open-source BitTorrent...
Chart Type
Set me up:
helm repo add center https://repo.chartcenter.io
Install Chart:
helm install qbittorrent center/k8s-at-home/qbittorrent
Versions (0)


This is a helm chart for qbittorrent.

This chart is not maintained by the upstream project and any issues with the chart should be raised here


$ helm repo add k8s-at-home https://k8s-at-home.com/charts/
$ helm install k8s-at-home/qbittorrent

Installing the Chart

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

helm install --name my-release k8s-at-home/qbittorrent

The default login details (change ASAP) are:

  • login:admin
  • password:adminadmin

Uninstalling the Chart

To uninstall/delete the my-release deployment:

helm delete my-release --purge

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

Read through the charts values.yaml file. It has several commented out suggested values. Additionally you can take a look at the common library values.yaml for more (advanced) configuration options.

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

helm install my-release \
  --set env.TZ="America/New_York" \

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 k8s-at-home/qbittorrent --values values.yaml 
  tag: ...


If you get

Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...`

it may be because you uninstalled the chart with skipuninstall enabled, you need to manually delete the pvc or use existingClaim.

Upgrading an existing Release to a new major version

A major chart version change (like 4.0.1 -> 5.0.0) indicates that there is an incompatible breaking change potentially needing manual actions.

Upgrading from 5.x.x to 6.x.x

Due to migrating to a centralized common library some values in values.yaml have changed.


  • service.port has been moved to service.port.port.
  • persistence.type has been moved to controllerType.

Refer to the library values.yaml for more configuration options.