9819265d4e
* initial grocy build Signed-off-by: Ryan Holt <ryan@Ryans-iMac.holthome.net> * forgot the helper file Signed-off-by: Ryan Holt <ryan@ryanholt.net> * remove comments Signed-off-by: Ryan Holt <ryan@ryanholt.net> * change to port 80 Signed-off-by: Ryan Holt <ryan@ryanholt.net> * add liveness probe Signed-off-by: Ryan Holt <ryan@ryanholt.net> * helps if the probes are actually defined in values Signed-off-by: Ryan Holt <ryan@ryanholt.net> * adding more time for readiness probe Signed-off-by: Ryan Holt <ryan@ryanholt.net> * flip from readiness to liveness Signed-off-by: Ryan Holt <ryan@ryanholt.net> * add startup probe, revert readiness/liveness to default Signed-off-by: Ryan Holt <ryan@ryanholt.net> * remove readiness probe Signed-off-by: Ryan Holt <ryan@ryanholt.net> * remove startupprobe, change default liveness and readiness to higher numbers Signed-off-by: Ryan Holt <ryan@ryanholt.net> * trying the startupProbe again * fix indentations * that wasn't a fix * definitely not right * bump up default values * change from timeoutSeconds to periodSeconds * rename the value variable * add timeoutSeconds back in * update readme and chart owner Signed-off-by: Ryan Holt <ryan@ryanholt.net> |
||
---|---|---|
.. | ||
templates | ||
.helmignore | ||
Chart.yaml | ||
OWNERS | ||
README.md | ||
values.yaml |
Grocy
This is a helm chart for Grocy leveraging the Linuxserver.io image
TL;DR;
$ helm repo add billimek https://billimek.com/billimek-charts/
$ helm install billimek/grocy
Installing the Chart
To install the chart with the release name my-release
:
helm install --name my-release billimek/grocy
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/grocy |
image.tag |
Image tag. Possible values listed here. | v2.6.1-ls51 |
image.pullPolicy |
Image pull policy | IfNotPresent |
strategyType |
Specifies the strategy used to replace old Pods by new ones | Recreate |
timezone |
Timezone the grocy instance should run as, e.g. 'America/New_York' | UTC |
puid |
process userID the grocy instance should run as | 1000 |
pgid |
process groupID the grocy instance should run as | 1000 |
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.liveness.periodSeconds |
Specify liveness periodSeconds 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 |
probes.readiness.periodSeconds |
Specify readiness periodSeconds parameter for the deployment |
10 |
Service.type |
Kubernetes service type for the grocy GUI | ClusterIP |
Service.port |
Kubernetes port where the grocy GUI is exposed | 9283 |
Service.annotations |
Service annotations for the grocy GUI | {} |
Service.labels |
Custom labels | {} |
Service.loadBalancerIP |
Loadbalance IP for the grocy GUI | {} |
Service.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 |
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" \
billimek/grocy
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 billimek/grocy
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.