History

kjeld Schouten-Lebbing 91b7bc2c40 Add Stage-3 Apps Please consider all these as mostly feature complete BETA Apps for the time being Co-authored-by: Troy Prelog <35702532+tprelog@users.noreply.github.com> Signed-off-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl>		2021-02-10 11:09:33 +01:00
..
charts	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
templates	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
.helmignore	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
Chart.yaml	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
README.md	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
app-readme.md	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
questions.yaml	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
test_values.yaml	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00
values.yaml	Add Stage-3 Apps	2021-02-10 11:09:33 +01:00

README.md

Nzbhydra2

This is a helm chart for Nzbhydra2.

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

TL;DR;

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

Installing the Chart

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

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

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

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 nzbhydra2 \
  --set env.TZ="America/New_York" \
    k8s-at-home/nzbhydra2

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

helm install nzbhydra2 k8s-at-home/nzbhydra2 --values values.yaml

image:
  tag: ...

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.

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 3.x.x to 4.x.x

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

Examples:

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.