e368075ba5
* Update Helm chart common to v0.12.0 * Update-Folder-Names-and-Dependencies Co-authored-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: renovate[bot] <renovate[bot]@users.noreply.github.com> |
||
---|---|---|
.. | ||
charts | ||
templates | ||
.helmignore | ||
Chart.lock | ||
Chart.yaml | ||
README.md | ||
app-readme.md | ||
questions.yaml | ||
test_values.yaml | ||
values.yaml |
README.md
LazyLibrarian
This is a helm chart for LazyLibrarian based on the container image provided by LinuxServer.io.
TL;DR
$ helm repo add k8s-at-home https://k8s-at-home.com/charts/
$ helm install k8s-at-home/lazylibrarian
Installing the Chart
To install the chart with the release name my-release
:
helm install --name my-release k8s-at-home/lazylibrarian
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 lazylibrarian \
--set env.TZ="America/New_York" \
k8s-at-home/lazylibrarian
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
helm install lazylibrarian k8s-at-home/lazylibrarian --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 2.x.x to 3.x.x
Due to migrating to a centralized common library some values in values.yaml
have changed.
Examples:
pguid
has been moved toenv
pgid
has been moved toenv
- All dockermods have been moved to
env
service.port
has been moved toservice.port.port
.persistence.type
has been moved tocontrollerType
.
Refer to the library values.yaml for more configuration options.