This is a helm chart for deluge leveraging the Linuxserver.io image. This Chart is heavily based on the format used by billimek for his collection of media related charts.

TL;DR;

$ helm repo add nikdoof https://nikdoof.github.io/helm-charts/
$ helm install deluge

Installing the Chart

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

helm install --name my-release deluge

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.

Configuration

The following tables lists the configurable parameters of the Sentry chart and their default values.

Parameter	Description	Default
`image.repository`	Image repository	`linuxserver/deluge`
`image.tag`	Image tag. Possible values listed here.	`2.0.3-2201906121747ubuntu18.04.1-ls57`
`image.pullPolicy`	Image pull policy	`IfNotPresent`
`strategyType`	Specifies the strategy used to replace old Pods by new ones	`Recreate`
`timezone`	Timezone the deluge instance should run as, e.g. 'America/New_York'	`UTC`
`puid`	process userID the deluge instance should run as	`1001`
`pgid`	process groupID the deluge instance should run as	`1001`
`probes.liveness.initialDelaySeconds`	Specify liveness `initialDelaySeconds` parameter for the deployment	`60`
`probes.liveness.failureThreshold`	Specify liveness `failureThreshold` parameter for the deployment	`5`
`probes.liveness.timeoutSeconds`	Specify liveness `timeoutSeconds` parameter for the deployment	`10`
`probes.readiness.initialDelaySeconds`	Specify readiness `initialDelaySeconds` parameter for the deployment	`60`
`probes.readiness.failureThreshold`	Specify readiness `failureThreshold` parameter for the deployment	`5`
`probes.readiness.timeoutSeconds`	Specify readiness `timeoutSeconds` parameter for the deployment	`10`
`webUiService.type`	Kubernetes service type for the deluge GUI	`ClusterIP`
`webUiService.port`	Kubernetes port where the deluge GUI is exposed	`8112`
`webUiService.annotations`	Service annotations for the deluge GUI	`{}`
`webUiService.labels`	Custom labels	`{}`
`webUiService.loadBalancerIP`	Loadbalance IP for the deluge GUI	`{}`
`webUiService.loadBalancerSourceRanges`	List of IP CIDRs allowed access to load balancer (if supported)	None
`btService.type`	Kubernetes service type for the deluge Bittorrent ports	`NodePort`
`btService.annotations`	Service annotations for the deluge Bittorrent ports	`{}`
`btService.labels`	Custom labels	`{}`
`btService.loadBalancerIP`	Loadbalance IP for the deluge Bittorrent ports	`{}`
`btService.loadBalancerSourceRanges`	List of IP CIDRs allowed access to load balancer (if supported)	None
`ingress.enabled`	Enables Ingress	`false`
`ingress.annotations`	Ingress annotations	`{}`
`ingress.labels`	Custom labels	`{}`
`ingress.path`	Ingress path	`/`
`ingress.hosts`	Ingress accepted hostnames	`chart-example.local`
`ingress.tls`	Ingress TLS configuration	`[]`
`persistence.config.enabled`	Use persistent volume to store configuration data	`true`
`persistence.config.size`	Size of persistent volume claim	`1Gi`
`persistence.config.existingClaim`	Use an existing PVC to persist data	`nil`
`persistence.config.subPath`	Mount a sub directory of the persistent volume if set	`""`
`persistence.config.storageClass`	Type of persistent volume claim	`-`
`persistence.config.accessMode`	Persistence access mode	`ReadWriteOnce`
`persistence.config.skipuninstall`	Do not delete the pvc upon helm uninstall	`false`
`persistence.downloads.enabled`	Use persistent volume to store downloads	`true`
`persistence.downloads.size`	Size of persistent volume claim	`1Gi`
`persistence.downloads.existingClaim`	Use an existing PVC to persist data	`nil`
`persistence.downloads.subPath`	Mount a sub directory of the persistent volume if set	`""`
`persistence.downloads.storageClass`	Type of persistent volume claim	`-`
`persistence.downloads.accessMode`	Persistence access mode	`ReadWriteOnce`
`persistence.downloads.skipuninstall`	Do not delete the pvc upon helm uninstall	`false`
`persistence.extraExistingClaimMounts`	Optionally add multiple existing claims to the container	`[]`
`resources`	CPU/Memory resource requests/limits	`{}`
`nodeSelector`	Node labels for pod assignment	`{}`
`tolerations`	Toleration labels for pod assignment	`[]`
`affinity`	Affinity settings for pod assignment	`{}`
`podAnnotations`	Key-value pairs to add as pod annotations	`{}`
`deploymentAnnotations`	Key-value pairs to add as deployment annotations	`{}`

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

helm install --name my-release \
  --set timezone="America/New York" \
    ./deluge

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

helm install --name my-release -f values.yaml ./deluge

NOTE

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.

Read through the values.yaml file. It has several commented out suggested values.