diff --git a/.submodules/kube-plex b/.submodules/kube-plex deleted file mode 160000 index 24056f11..00000000 --- a/.submodules/kube-plex +++ /dev/null @@ -1 +0,0 @@ -Subproject commit 24056f110d5b135121e0900dece9b44eca9ac736 diff --git a/README.md b/README.md index 3e0aeb8f..40bbab96 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,3 @@ -[![CircleCI](https://circleci.com/gh/billimek/billimek-charts.svg?style=svg)](https://circleci.com/gh/billimek/billimek-charts) - # Collection of helm charts ## Installation diff --git a/_config.yml b/_config.yml index c4192631..e9a60bb7 100644 --- a/_config.yml +++ b/_config.yml @@ -1 +1,3 @@ -theme: jekyll-theme-cayman \ No newline at end of file +theme: jekyll-theme-cayman +name: billimek Helm Charts +description: billimek-charts Helm Repository \ No newline at end of file diff --git a/cloudflare-dyndns/README.md b/cloudflare-dyndns/README.md deleted file mode 100644 index a77e94a7..00000000 --- a/cloudflare-dyndns/README.md +++ /dev/null @@ -1,67 +0,0 @@ -# Dynamic DNS using Cloudflare's DNS Services - -A script that pushes the public IP address of the running machine to Cloudflare's DNS API's. It requires an existing A record to update. - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/cloudflare-dyndns -``` - -## Introduction - -This code is adopted from [this original repo](https://github.com/hotio/docker-cloudflare-ddns) - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/cloudflare-dyndns -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ 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` | cloudflare-dyndns image | `hotio/cloudflare-ddns` | -| `image.tag` | cloudflare-dyndns image tag | `latest` | -| `image.pullPolicy` | cloudflare-dyndns image pull policy | `Always` | -| `cloudflare.user` | The username of your Cloudflare account, should be your email address. | `` | -| `cloudflare.token` | The token you generated in Cloudflare's API settings. | `` | -| `cloudflare.zones` | The domain(s) you wish to update, separated by `;` | `` | -| `cloudflare.hosts` | The subdomain(s) you wish to update, separated by `;` | `` | -| `cloudflare.record_types` | The record types to update, separated by `;` | `` | -| `cloudflare.detection_mode` | Source to query for public IP | `dig-google.com` | -| `cloudflare.log_level` | Verbosity of the logs printed to stdout/stderr | `1` | -| `cloudflare.sleep_interval` | Polling time in seconds | `300` | - - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set config.cloudflare.token=thisismyapikey \ - billimek/cloudflare-dyndns -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/cloudflare-dyndns -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/cloudflare-dyndns/values.yaml) file. It has several commented out suggested values. diff --git a/comcast/README.md b/comcast/README.md deleted file mode 100644 index 01509393..00000000 --- a/comcast/README.md +++ /dev/null @@ -1,84 +0,0 @@ -# Comcast Data Cap Usage Collector For InfluxDB and Grafana - -![Screenshot](https://github.com/billimek/comcastUsage-for-influxdb/raw/master/images/comcast_grafana_example.png) - -This tool allows you to run periodic comcast data usage checks and save the results to Influxdb - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/comcast -``` - -## Introduction - -This code is adopted from the work done by [barrycarey](https://github.com/barrycarey) in the [similar thing for capturing speedtest data](https://github.com/barrycarey/Speedtest-for-InfluxDB-and-Grafana) as well as [jantman's](https://github.com/jantman) [xfinity-usage python example](https://github.com/jantman/xfinity-usage) - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/comcast -``` -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ helm delete my-release --purge -``` - -The command removes all the Kubernetes components associated with the chart and deletes the release. - -## Configuration - -The configuration is set as a block of text through a configmap and mounted as a file in /src/config.ini Any value in this text block should match the defined Comcast configuration. There are several values here that will have to match our kubernetes configuration. - -## Configuration - -The following tables lists the configurable parameters of the Sentry chart and their default values. - -| Parameter | Description | Default | -| ------------------------------- | ------------------------------- | ---------------------------------------------------------- | -| `image.repository` | Comcast image | `billimek/comcastusage-for-influxdb` | -| `image.tag` | Comcast image tag | `latest` | -| `image.pullPolicy` | Comcast image pull policy | `IfNotPresent` | -| `debug` | Display debugging output | `false` | -| `config.delay` | how many seconds to wait between checks | `3600` | -| `config.influxdb.host` | InfluxDB hostname | `influxdb-influxdb` | -| `config.influxdb.port` | InfluxDB port | `8086` | -| `config.influxdb.database` | InfluxDB database | `comcast` | -| `config.influxdb.username` | InfluxDB username | `` | -| `config.influxdb.password` | InfluxDB password | `` | -| `config.influxdb.ssl` | InfluxDB connection using SSL | `false` | -| `config.comcast.username` | Comcast website login usernma | `someuser` | -| `config.comcast.password` | Comcast website login password | `somepassword` | -| `podAnnotations` | Key-value pairs to add as pod annotations | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set config.comcast.username=tonystark,config.comcast.password=mypassword \ - billimek/comcast -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/comcast -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/comcast/values.yaml) file. It has several commented out suggested values. - -## InfluxDB metrics -``` -'measurement': 'comcast_data_usage', -'fields': { - 'used', - 'total', - 'unit' -} -``` \ No newline at end of file diff --git a/digitalocean-dyndns/README.md b/digitalocean-dyndns/README.md deleted file mode 100644 index dce01f4b..00000000 --- a/digitalocean-dyndns/README.md +++ /dev/null @@ -1,62 +0,0 @@ -# Dynamic DNS using DigitalOcean's DNS Services - -A script that pushes the public IP address of the running machine to DigitalOcean's DNS API's. It requires an existing A record to update. The resulting container image is roughly around 7 MB (thanks to Alpine Linux). - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/digitalocean-dyndns -``` - -## Introduction - -This code is adopted from [this original repo](https://github.com/tunix/digitalocean-dyndns) - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/digitalocean-dyndns -``` -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ 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` | digitalocean-dyndns image | `tunix/digitalocean-dyndns` | -| `image.tag` | digitalocean-dyndns image tag | `latest` | -| `image.pullPolicy` | digitalocean-dyndns image pull policy | `Always` | -| `digitialocean.token` | The token you generate in DigitalOcean's API settings. | `` | -| `digitialocean.domain` | The domain your subdomain is registered at. (i.e. foo.com for home.foo.com) | `` | -| `digitialocean.name` | Subdomain to use. (name in A record) (i.e. home for home.foo.com or @ for no subdomain) | `@` | -| `digitialocean.sleep_interval` | Polling time in seconds | `300` | - - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set config.digitalocean.token=thisismyapikey \ - billimek/digitalocean-dyndns -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/digitalocean-dyndns -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/digitalocean-dyndns/values.yaml) file. It has several commented out suggested values. diff --git a/frigate/README.md b/frigate/README.md deleted file mode 100644 index 531f4abe..00000000 --- a/frigate/README.md +++ /dev/null @@ -1,92 +0,0 @@ -# frigate: Realtime object detection on RTSP cameras with the Google Coral - -This is a helm chart for [frigate](https://github.com/blakeblackshear/frigate) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/frigate -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/frigate -``` - -**IMPORTANT NOTE:** the [Google Coral USB Accelerator](https://coral.withgoogle.com/products/accelerator/) must be accessible on the node where this pod runs, in order for this chart to function properly. - -A way to achieve this can be with nodeAffinity rules, for example: - -```yaml -affinity: - nodeAffinity: - requiredDuringSchedulingIgnoredDuringExecution: - nodeSelectorTerms: - - matchExpressions: - - key: tpu - operator: In - values: - - google-coral -``` - -... where a node with an attached Coral USB device is labeled with `tpu: google-coral` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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 | `blakeblackshear/frigate` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/blakeblackshear/frigate/tags/).| `0.2.0`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the frigate instance should run as, e.g. 'America/New_York' | `UTC` | -| `rtspPassword` | Password to use for RTSP cameras | `password` | -| `config` | frigate configuration - see [config.yaml](https://github.com/blakeblackshear/frigate/blob/master/config/config.yml) for example | `{}` | -| `Service.type` | Kubernetes service type for the frigate GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the frigate GUI is exposed| `5000` | -| `Service.annotations` | Service annotations for the frigate GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the frigate 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 | `[]` | -| `resources` | CPU/Memory resource requests/limits | `{}` | -| `nodeSelector` | Node labels for pod assignment | `{}` | -| `tolerations` | Toleration labels for pod assignment | `[]` | -| `affinity` | Affinity settings for pod assignment | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set rtspPassword="nosecrets" \ - billimek/frigate -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml stable/frigate -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/frigate/values.yaml) file. It has several commented out suggested values. diff --git a/home-assistant/README.md b/home-assistant/README.md deleted file mode 100644 index 5ffcbe04..00000000 --- a/home-assistant/README.md +++ /dev/null @@ -1 +0,0 @@ -The Home Assistant chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/home-assistant diff --git a/index.md b/index.md new file mode 100644 index 00000000..1ba65a90 --- /dev/null +++ b/index.md @@ -0,0 +1,18 @@ +# Collection of helm charts + +## Usage + +[Helm](https://helm.sh) must be installed to use the charts. +Please refer to Helm's [documentation](https://helm.sh/docs/) to get started. + +Once Helm is set up properly, add the repo as follows: + +```console +helm repo add billimek https://billimek.com/billimek-charts/ +``` + +You can then run `helm search repo billimek` to see the charts. + +## Charts + +See [helm hub](https://hub.helm.sh/charts/billimek) for a complete list. diff --git a/jackett/README.md b/jackett/README.md deleted file mode 100644 index 9c93f355..00000000 --- a/jackett/README.md +++ /dev/null @@ -1,87 +0,0 @@ -# Jackett - -This is a helm chart for [Jackett](https://github.com/Jackett/Jackett) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/jackett/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/jackett -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/jackett -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/jackett` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/jackett/tags/).| `v0.12.1132-ls37`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the Jackett instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the Jackett instance should run as | `1001` | -| `pgid` | process groupID the Jackett instance should run as | `1001` | -| `probes.liveness.failureThreshold` | Specify liveness `failureThreshold` parameter for the deployment | `5` | -| `probes.liveness.periodSeconds` | Specify liveness `periodSeconds` parameter for the deployment | `10` | -| `probes.readiness.failureThreshold` | Specify readiness `failureThreshold` parameter for the deployment | `5` | -| `probes.readiness.periodSeconds` | Specify readiness `periodSeconds` parameter for the deployment | `10` | -| `probes.startup.initialDelaySeconds` | Specify startup `initialDelaySeconds` parameter for the deployment | `5` | -| `probes.startup.failureThreshold` | Specify startup `failureThreshold` parameter for the deployment | `30` | -| `probes.startup.periodSeconds` | Specify startup `periodSeconds` parameter for the deployment | `10` | -| `Service.type` | Kubernetes service type for the Jackett GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the Jackett GUI is exposed| `9117` | -| `Service.annotations` | Service annotations for the Jackett GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the Jackett 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/jackett -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/jackett -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/jackett/values.yaml) file. It has several commented out suggested values. \ No newline at end of file diff --git a/kube-plex/README.md b/kube-plex/README.md deleted file mode 100644 index 7a505c09..00000000 --- a/kube-plex/README.md +++ /dev/null @@ -1,49 +0,0 @@ -# Plex Media Server helm chart - -## Configuration - -The following tables lists the configurable parameters of the Plex chart and their default values. - -| Parameter | Description | Default | -|----------------------------|-------------------------------------|---------------------------------------------------------| -| `image.repository` | Image repository | `plexinc/pms-docker` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/plexinc/pms-docker/tags/).| `1.10.1.4602-f54242b6b`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `kubePlex.enabled` | Enable KubPlex transcoder | `true` | -| `kubePlex.image.repository` | Image repository | `quay.io/munnerz/kube-plex` | -| `kubePlex.image.tag` | Image tag. | `latest`| -| `kubePlex.image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `claimToken` | Plex Claim Token to authenticate your acount | `` | -| `timezone` | Timezone plex instance should run as, e.g. 'America/New_York' | `Europe/London` | -| `service.type` | Kubernetes service type for the plex GUI/API | `ClusterIP` | -| `service.port` | Kubernetes port where the plex GUI/API is exposed| `32400` | -| `service.annotations` | Service annotations for the Plex GUI | `{}` | -| `service.labels` | Custom labels | `{}` | -| `service.loadBalancerIP` | Loadbalance IP for the Plex 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 | `[]` | -| `rbac.create` | Create RBAC roles? | `true` | -| `nodeSelector` | Node labels for pod assignment | `beta.kubernetes.io/arch: amd64` | -| `persistence.transcode.enabled` | Use persistent volume for transcoding | `false` | -| `persistence.transcode.size` | Size of persistent volume claim | `20Gi` | -| `persistence.transcode.claimName`| Use an existing PVC to persist data | `nil` | -| `persistence.transcode.subPath` | SubPath to use for existing Claim | `nil` | -| `persistence.transcode.storageClass` | Type of persistent volume claim | `-` | -| `persistence.data.size` | Size of persistent volume claim | `40Gi` | -| `persistence.data.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.data.subPath` | SubPath to use for existing Claim | `nil` | -| `persistence.data.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.size` | Size of persistent volume claim | `20Gi` | -| `persistence.config.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.config.subPath` | SubPath to use for existing Claim | `nil` | -| `persistence.config.storageClass` | Type of persistent volume claim | `-` | -| `resources` | CPU/Memory resource requests/limits | `{}` | -| `podAnnotations` | Key-value pairs to add as pod annotations | `{}` | - - -Read through the [values.yaml](values.yaml) file. It has several commented out suggested values. diff --git a/modem-stats/README.md b/modem-stats/README.md deleted file mode 100644 index 1ee2ea38..00000000 --- a/modem-stats/README.md +++ /dev/null @@ -1,69 +0,0 @@ -# cable modem (sb6183) signal and stats collection agent for influxdb - -![Screenshot](https://camo.githubusercontent.com/939e044c0491abf790d91bd1d7f909b187e4098c/68747470733a2f2f692e696d6775722e636f6d2f70705a6a6e6b502e706e67) - -This tool allows you to run periodic scanning of the sb6183 cable modem and save the results to Influxdb - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/modem-stats -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/modem-stats -``` -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ helm delete my-release --purge -``` - -The command removes all the Kubernetes components associated with the chart and deletes the release. - -## Configuration - -The configuration is set as a block of text through a configmap and mouted as a file in /src/config.ini Any value in this text block should match the defined sb6183 configuration. There are several values here that will have to match our kubernetes configuration. - -## Configuration - -The following tables lists the configurable parameters of the Sentry chart and their default values. - -| Parameter | Description | Default | -| ------------------------------- | ------------------------------- | ---------------------------------------------------------- | -| `image.repository` | modem-stats image | `billimek/sb6183-for-influxdb` | -| `image.tag` | modem-stats image tag | `latest` | -| `image.pullPolicy` | modem-stats image pull policy | `IfNotPresent` | -| `debug` | Display debugging output | `false` | -| `config.delay` | how many seconds to wait between checks | `3600` | -| `config.influxdb.host` | InfluxDB hostname | `influxdb-influxdb` | -| `config.influxdb.port` | InfluxDB port | `8086` | -| `config.influxdb.database` | InfluxDB database | `sb6183` | -| `config.influxdb.username` | InfluxDB username | `` | -| `config.influxdb.password` | InfluxDB password | `` | -| `config.influxdb.ssl` | InfluxDB connection using SSL | `false` | -| `config.modem.url` | sb6183 stats URL page | `http://192.168.100.1/RgConnect.asp` | -| `podAnnotations` | Key-value pairs to add as pod annotations | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -$ helm install --name my-release \ - --set onfig.influxdb.host=some-influx-host \ - billimek/modem-stats -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -$ helm install --name my-release -f values.yaml billimek/modem-stats -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/modem-stats/values.yaml) file. It has several commented out suggested values. diff --git a/node-red/README.md b/node-red/README.md deleted file mode 100644 index c0221ef0..00000000 --- a/node-red/README.md +++ /dev/null @@ -1 +0,0 @@ -The node-red chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/node-red diff --git a/nzbget/README.md b/nzbget/README.md deleted file mode 100644 index 0ffb7d5a..00000000 --- a/nzbget/README.md +++ /dev/null @@ -1,96 +0,0 @@ -# NZBGet Usenet client - -This is a helm chart for [NZBGet](https://nzbget.net/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/nzbget/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/nzbget -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/nzbget -``` - -The default login details (change ASAP) are: - -* login:nzbget -* password:tegbzn6789 - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/nzbget` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/nzbget/tags/).| `v21.0-ls14`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the nzbget instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the nzbget instance should run as | `1001` | -| `pgid` | process groupID the nzbget 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` | -| `Service.type` | Kubernetes service type for the nzbget GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the nzbget GUI is exposed| `6789` | -| `Service.annotations` | Service annotations for the nzbget GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the nzbget 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.downloads.enabled` | Use persistent volume to store configuration data | `true` | -| `persistence.downloads.size` | Size of persistent volume claim | `10Gi` | -| `persistence.downloads.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.downloads.storageClass` | Type of persistent volume claim | `-` | -| `persistence.downloads.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/nzbget -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml stable/nzbget -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/nzbget/values.yaml) file. It has several commented out suggested values. \ No newline at end of file diff --git a/nzbhydra2/README.md b/nzbhydra2/README.md deleted file mode 100644 index 944ed3ab..00000000 --- a/nzbhydra2/README.md +++ /dev/null @@ -1,87 +0,0 @@ -# nzbhydra2 - -This is a helm chart for [nzbhydra2](https://github.com/theotherp/nzbhydra2) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/hydra2/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/nzbhydra2 -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/nzbhydra2 -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/hydra2` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/hydra2/tags/).| `v0.12.1132-ls37`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the nzbhydra2 instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the nzbhydra2 instance should run as | `1001` | -| `pgid` | process groupID the nzbhydra2 instance should run as | `1001` | -| `probes.liveness.failureThreshold` | Specify liveness `failureThreshold` parameter for the deployment | `5` | -| `probes.liveness.periodSeconds` | Specify liveness `periodSeconds` parameter for the deployment | `10` | -| `probes.readiness.failureThreshold` | Specify readiness `failureThreshold` parameter for the deployment | `5` | -| `probes.readiness.periodSeconds` | Specify readiness `periodSeconds` parameter for the deployment | `10` | -| `probes.startup.initialDelaySeconds` | Specify startup `initialDelaySeconds` parameter for the deployment | `5` | -| `probes.startup.failureThreshold` | Specify startup `failureThreshold` parameter for the deployment | `30` | -| `probes.startup.periodSeconds` | Specify startup `periodSeconds` parameter for the deployment | `10` | -| `Service.type` | Kubernetes service type for the nzbhydra2 GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the nzbhydra2 GUI is exposed| `5076` | -| `Service.annotations` | Service annotations for the nzbhydra2 GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the nzbhydra2 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/nzbhydra2 -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/nzbhydra2 -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/nzbhydra2/values.yaml) file. It has several commented out suggested values. diff --git a/ombi/README.md b/ombi/README.md deleted file mode 100644 index 4f2ac830..00000000 --- a/ombi/README.md +++ /dev/null @@ -1,86 +0,0 @@ -# Ombi - -This is a helm chart for [Ombi](https://ombi.io/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/ombi/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/ombi -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/ombi -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/ombi` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/ombi/tags/).| `3.0.4914-ls72`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the Ombi instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the Ombi instance should run as | `1001` | -| `pgid` | process groupID the Ombi 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` | -| `Service.type` | Kubernetes service type for the Ombi GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the Ombi GUI is exposed| `3579` | -| `Service.annotations` | Service annotations for the Ombi GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the Ombi 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/ombi -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/ombi -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/ombi/values.yaml) file. It has several commented out suggested values. \ No newline at end of file diff --git a/qbittorrent/README.md b/qbittorrent/README.md deleted file mode 100644 index fb378959..00000000 --- a/qbittorrent/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# qBitTorrent client - -TBD \ No newline at end of file diff --git a/radarr/README.md b/radarr/README.md deleted file mode 100644 index 1f22cc91..00000000 --- a/radarr/README.md +++ /dev/null @@ -1,97 +0,0 @@ -# radarr movie download client - -This is a helm chart for [radarr](https://github.com/Radarr/Radarr/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/radarr/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/radarr -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/radarr -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/radarr` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/radarr/tags/).| `amd64-v0.2.0.1344-ls17`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the radarr instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the radarr instance should run as | `1001` | -| `pgid` | process groupID the radarr 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` | -| `Service.type` | Kubernetes service type for the radarr GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the radarr GUI is exposed| `7878` | -| `Service.annotations` | Service annotations for the radarr GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the radarr 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.downloads.enabled` | Use persistent volume to store configuration data | `true` | -| `persistence.downloads.size` | Size of persistent volume claim | `10Gi` | -| `persistence.downloads.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.downloads.storageClass` | Type of persistent volume claim | `-` | -| `persistence.downloads.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.movies.enabled` | Use persistent volume to store configuration data | `true` | -| `persistence.movies.size` | Size of persistent volume claim | `10Gi` | -| `persistence.movies.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.movies.storageClass` | Type of persistent volume claim | `-` | -| `persistence.movies.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.extraExistingClaimMounts` | Optionally add multiple existing claims | `[]` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/radarr -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml stable/radarr -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/radarr/values.yaml) file. It has several commented out suggested values. \ No newline at end of file diff --git a/rtorrent-flood/README.md b/rtorrent-flood/README.md deleted file mode 100644 index 983a0e3e..00000000 --- a/rtorrent-flood/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# rTorrent/flood BitTorrent client - -TBD \ No newline at end of file diff --git a/ser2sock/README.md b/ser2sock/README.md deleted file mode 100644 index df84bfa4..00000000 --- a/ser2sock/README.md +++ /dev/null @@ -1,86 +0,0 @@ -# ser2sock: Serial to Socket Redirector - -This is a helm chart for [ser2sock](https://github.com/nutechsoftware/ser2sock) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/ser2sock -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/ser2sock -``` - -**IMPORTANT NOTE:** the USB device must be accessible on the node where this pod runs, in order for this chart to function properly. - -A way to achieve this can be with nodeAffinity rules, for example: - -```yaml -affinity: - nodeAffinity: - requiredDuringSchedulingIgnoredDuringExecution: - nodeSelectorTerms: - - matchExpressions: - - key: usb - operator: In - values: - - alarmdecoder -``` - -... where a node with an attached Coral USB device is labeled with `usb: alarmdecoder` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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 | `tenstartups/ser2sock` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/tenstartups/ser2sock/tags).| `latest`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the ser2sock instance should run as, e.g. 'America/New_York' | `` | -| `device` | USB Device to use | `/dev/ttyUSB0` | -| `puid` | UID to run as | `1001` | -| `pgid` | GID to run as | `1001` | -| `Service.type` | Kubernetes service type for the ser2sock GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the ser2sock GUI is exposed| `5000` | -| `Service.annotations` | Service annotations for the ser2sock GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the ser2sock GUI | `{}` | -| `Service.loadBalancerSourceRanges` | List of IP CIDRs allowed access to load balancer (if supported) | None -| `resources` | CPU/Memory resource requests/limits | `{}` | -| `nodeSelector` | Node labels for pod assignment | `{}` | -| `tolerations` | Toleration labels for pod assignment | `[]` | -| `affinity` | Affinity settings for pod assignment | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - billimek/ser2sock -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/ser2sock -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/ser2sock/values.yaml) file. It has several commented out suggested values. diff --git a/sonarr/README.md b/sonarr/README.md deleted file mode 100644 index 255eebe4..00000000 --- a/sonarr/README.md +++ /dev/null @@ -1,97 +0,0 @@ -# sonarr televsion show download client - -This is a helm chart for [sonarr](https://github.com/sonarr/sonarr/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/sonarr/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/sonarr -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/sonarr -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/sonarr` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/sonarr/tags/).| `amd64-2.0.0.5321-ls62`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the sonarr instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the sonarr instance should run as | `1001` | -| `pgid` | process groupID the sonarr 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` | -| `Service.type` | Kubernetes service type for the sonarr GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the sonarr GUI is exposed| `8989` | -| `Service.annotations` | Service annotations for the sonarr GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the sonarr 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.downloads.enabled` | Use persistent volume for downloads | `true` | -| `persistence.downloads.size` | Size of persistent volume claim | `10Gi` | -| `persistence.downloads.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.downloads.storageClass` | Type of persistent volume claim | `-` | -| `persistence.downloads.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.tv.enabled` | Use persistent volume for tv show persistence | `true` | -| `persistence.tv.size` | Size of persistent volume claim | `10Gi` | -| `persistence.tv.existingClaim`| Use an existing PVC to persist data | `nil` | -| `persistence.tv.storageClass` | Type of persistent volume claim | `-` | -| `persistence.tv.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `persistence.extraExistingClaimMounts` | Optionally add multiple existing claims | `[]` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/sonarr -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml stable/sonarr -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/sonarr/values.yaml) file. It has several commented out suggested values. diff --git a/speedtest/README.md b/speedtest/README.md deleted file mode 100644 index 37a789dd..00000000 --- a/speedtest/README.md +++ /dev/null @@ -1,72 +0,0 @@ -# Speedtest.net Collector For InfluxDB and Grafana - -![Screenshot](https://camo.githubusercontent.com/c652a6685bcb5a8cec6a47c92e57d159b28e47e7/68747470733a2f2f7075752e73682f746d664f412f623535373665383864652e706e67) - -This tool is a wrapper for speedtest-cli which allows you to run periodic speedtets and save the results to Influxdb - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/speedtest -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/speedtest -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ helm delete my-release --purge -``` - -The command removes all the Kubernetes components associated with the chart and deletes the release. - -## Configuration - -The configuration is set as a block of text through a configmap and mounted as a file in /src/config.ini Any value in this text block should match the defined speedtest configuration. There are several values here that will have to match our kubernetes configuration. - -## Configuration - -The following tables lists the configurable parameters of the Sentry chart and their default values. - -| Parameter | Description | Default | -| ------------------------------- | ------------------------------- | ---------------------------------------------------------- | -| `image.repository` | speedtest image | `billimek/speedtestusage-for-influxdb` | -| `image.tag` | speedtest image tag | `latest` | -| `image.pullPolicy` | speedtest image pull policy | `IfNotPresent` | -| `debug` | Display debugging output | `false` | -| `config.delay` | how many seconds to wait between checks | `3600` | -| `config.influxdb.host` | InfluxDB hostname | `influxdb-influxdb` | -| `config.influxdb.port` | InfluxDB port | `8086` | -| `config.influxdb.database` | InfluxDB database | `speedtests` | -| `config.influxdb.username` | InfluxDB username | `` | -| `config.influxdb.password` | InfluxDB password | `` | -| `config.influxdb.ssl` | InfluxDB connection using SSL | `false` | -| `config.speedtest.server` | server to use for speedtest - leave blank to auto-pick | `` | -| `podAnnotations` | Key-value pairs to add as pod annotations | `{}` | - - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -$ helm install --name my-release \ - --set config.influxdb.host=some-influx-host \ - billimek/speedtest -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -$ helm install --name my-release -f values.yaml billimek/speedtest -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/speedtest/values.yaml) file. It has several commented out suggested values. - diff --git a/tautulli/README.md b/tautulli/README.md deleted file mode 100644 index 65c094f3..00000000 --- a/tautulli/README.md +++ /dev/null @@ -1,86 +0,0 @@ -# Tautulli - -This is a helm chart for [Tautulli](https://tautulli.com/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/tautulli/) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/tautulli -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name my-release billimek/tautulli -``` - -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -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/tautulli` | -| `image.tag` | Image tag. Possible values listed [here](https://hub.docker.com/r/linuxserver/tautulli/tags/).| `v2.1.39-ls32`| -| `image.pullPolicy` | Image pull policy | `IfNotPresent` | -| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` | -| `timezone` | Timezone the Tautulli instance should run as, e.g. 'America/New_York' | `UTC` | -| `puid` | process userID the Tautulli instance should run as | `1001` | -| `pgid` | process groupID the Tautulli 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` | -| `Service.type` | Kubernetes service type for the Tautulli GUI | `ClusterIP` | -| `Service.port` | Kubernetes port where the Tautulli GUI is exposed| `8181` | -| `Service.annotations` | Service annotations for the Tautulli GUI | `{}` | -| `Service.labels` | Custom labels | `{}` | -| `Service.loadBalancerIP` | Loadbalance IP for the Tautulli 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.storageClass` | Type of persistent volume claim | `-` | -| `persistence.config.accessMode` | Persistence access mode | `ReadWriteOnce` | -| `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 | `{}` | - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name my-release \ - --set timezone="America/New York" \ - billimek/tautulli -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name my-release -f values.yaml billimek/tautulli -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/tautulli/values.yaml) file. It has several commented out suggested values. \ No newline at end of file diff --git a/teslamate/README.md b/teslamate/README.md deleted file mode 100644 index c6802662..00000000 --- a/teslamate/README.md +++ /dev/null @@ -1,48 +0,0 @@ -# A self-hosted data logger for your Tesla 🚘 - -This is an opinionated helm chart for [Teslamate](https://github.com/adriankumpf/teslamate) installed with a standalone postgresql database. - -The default values and container images used in this chart will allow for running in a multi-arch cluster (amd64, arm, arm64) - -## TL;DR; - -```shell -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/teslamate -``` - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -helm install --name teslamate billimek/teslamate -``` - -## Uninstalling the Chart - -To uninstall/delete the `teslamate` deployment: - -```console -helm delete teslamate --purge -``` - -The command removes all the Kubernetes components associated with the chart and deletes the release. - -## Configuration - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/teslamate/values.yaml) file. It has several commented out suggested values. - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -helm install --name teslamate \ - --set timeZone="America/New York" \ - billimek/teslamate -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -helm install --name teslamate -f values.yaml stable/teslamate -``` diff --git a/teslamate/charts/postgresql-8.1.0.tgz b/teslamate/charts/postgresql-8.1.0.tgz deleted file mode 100644 index c30b14c0..00000000 Binary files a/teslamate/charts/postgresql-8.1.0.tgz and /dev/null differ diff --git a/unifi/README.md b/unifi/README.md deleted file mode 100644 index e678a2a6..00000000 --- a/unifi/README.md +++ /dev/null @@ -1 +0,0 @@ -The Unifi chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/unifi diff --git a/uptimerobot/README.md b/uptimerobot/README.md deleted file mode 100644 index f571c66d..00000000 --- a/uptimerobot/README.md +++ /dev/null @@ -1,73 +0,0 @@ -# A tool to get statistics from Uptime Robot and log it into InfluxDB - -![Screenshot](https://raw.githubusercontent.com/billimek/node-influx-uptimerobot/master/docs/dashboard.png) - -This tool allows you to run periodic uptimerobot data usage checks and save the results to Influxdb - -## TL;DR; - -```console -$ helm repo add billimek https://billimek.com/billimek-charts/ -$ helm install billimek/uptimerobot -``` - -## Introduction - -This code is adopted from [this original repo](https://github.com/trojanc/node-influx-uptimerobot) - -## Installing the Chart - -To install the chart with the release name `my-release`: - -```console -$ helm install --name my-release billimek/uptimerobot -``` -## Uninstalling the Chart - -To uninstall/delete the `my-release` deployment: - -```console -$ helm delete my-release --purge -``` - -The command removes all the Kubernetes components associated with the chart and deletes the release. - -## Configuration - -The configuration is set as a block of text through a configmap and mounted as a file in /src/config.ini Any value in this text block should match the defined uptimerobot configuration. There are several values here that will have to match our kubernetes configuration. - -## Configuration - -The following tables lists the configurable parameters of the Sentry chart and their default values. - -| Parameter | Description | Default | -| ------------------------------- | ------------------------------- | ---------------------------------------------------------- | -| `image.repository` | uptimerobot image | `billimek/uptimerobotusage-for-influxdb` | -| `image.tag` | uptimerobot image tag | `latest` | -| `image.pullPolicy` | uptimerobot image pull policy | `IfNotPresent` | -| `delay` | number of seconds to wait between collections | `300` | -| `config.influxdb.host` | InfluxDB hostname | `influxdb-influxdb` | -| `config.influxdb.port` | InfluxDB port | `8086` | -| `config.influxdb.database` | InfluxDB database | `uptimerobot` | -| `config.influxdb.protocol` | InfluxDB protocol | `http` | -| `config.influxdb.username` | InfluxDB username | `` | -| `config.influxdb.password` | InfluxDB password | `` | -| `config.uptimerobot.apikey` | uptimerobot API key (REQUIRED) | `someapikey` | -| `podAnnotations` | Key-value pairs to add as pod annotations | `{}` | - - -Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, - -```console -$ helm install --name my-release \ - --set config.uptimerobot.apikey=thisismyapikey \ - billimek/uptimerobot -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, - -```console -$ helm install --name my-release -f values.yaml billimek/uptimerobot -``` - -Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/uptimerobot/values.yaml) file. It has several commented out suggested values.