master-group/charts
2
0
Fork 0
mirror of https://github.com/k8s-at-home/charts.git synced 2025-01-23 23:49:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

deal with .deploy

Browse Source
This commit is contained in:
Jeff Billimek 2019-08-04 23:19:52 -04:00
parent 608d941497
commit 3eb5b11562
16 changed files with 1 additions and 963 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
.deploy/comcast-1.0.5.tgz
View File

Binary file not shown.

83
.deploy/docs/comcast/README.md
View File

@ -1,83 +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` |
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'
}
```

62
.deploy/docs/digitalocean-dyndns/README.md
View File

@ -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.

92
.deploy/docs/frigate/README.md
View File

@ -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.

1
.deploy/docs/home-assistant/README.md
View File

@ -1 +0,0 @@
The Home Assistant chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/home-assistant

68
.deploy/docs/modem-stats/README.md
View File

@ -1,68 +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` |
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.

1
.deploy/docs/node-red/README.md
View File

@ -1 +0,0 @@
The node-red chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/node-red

89
.deploy/docs/nzbget/README.md
View File

@ -1,89 +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` |
| `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 | `{}` |
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.

90
.deploy/docs/radarr/README.md
View File

@ -1,90 +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` |
| `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 | `{}` |
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.

3
.deploy/docs/rtorrent-flood/README.md
View File

@ -1,3 +0,0 @@
# rTorrent/flood BitTorrent client
TBD

90
.deploy/docs/sonarr/README.md
View File

@ -1,90 +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` |
| `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 | `{}` |
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.

70
.deploy/docs/speedtest/README.md
View File

@ -1,70 +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 | `` |
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.

1
.deploy/docs/unifi/README.md
View File

@ -1 +0,0 @@
The Unifi chart is now an official helm chart: https://github.com/helm/charts/tree/master/stable/unifi

71
.deploy/docs/uptimerobot/README.md
View File

@ -1,71 +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` |
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.

242
.deploy/index.yaml
View File

@ -1,242 +0,0 @@
apiVersion: v1
entries:
comcast:
- apiVersion: v1
appVersion: 1.0.0
created: "2019-08-05T03:05:45.024165793Z"
description: periodic comcast data usage checks and save the results to InfluxDB
digest: 46acd3d8ef4d63ef553418209c39de2e0a2339e8ffecb21d2e26dd4680fa8f4f
home: https://github.com/billimek/billimek-charts/tree/master/comcast
icon: https://i.imgur.com/iR1dUpp.png
keywords:
- comcast
- influxdb
- xfinity
maintainers:
- email: jeff@billimek.com
name: billimek
name: comcast
sources:
- https://github.com/billimek/comcastUsage-for-influxdb
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/comcast-1.0.5/comcast-1.0.5.tgz
version: 1.0.5
- apiVersion: v1
appVersion: 1.0.0
created: "2019-08-05T03:05:46.426452632Z"
description: periodic comcast data usage checks and save the results to InfluxDB
digest: 306e66407c47c58382eccd68616fdbb6ed498a444a023ffbb1534d0e087e6bc8
home: https://github.com/billimek/billimek-charts/tree/master/comcast
icon: https://i.imgur.com/iR1dUpp.png
keywords:
- comcast
- influxdb
- xfinity
maintainers:
- email: jeff@billimek.com
name: billimek
name: comcast
sources:
- https://github.com/billimek/comcastUsage-for-influxdb
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/comcast-1.0.4/comcast-1.0.4.tgz
version: 1.0.4
digitalocean-dyndns:
- apiVersion: v1
appVersion: "1.0"
created: "2019-08-05T03:05:46.2985357Z"
description: Dynamic DNS using DigitalOcean's DNS Services
digest: 7db7fc339ec946090c1339c1d4f0a741e6e7e99d11da0eacc4069ba3e93964cb
home: https://github.com/billimek/billimek-charts/tree/master/digitalocean-dyndns
icon: https://i.imgur.com/cS6iqXD.png
keywords:
- digitalocean
- dynamicdns
maintainers:
- email: jeff@billimek.com
name: billimek
name: digitalocean-dyndns
sources:
- https://github.com/tunix/digitalocean-dyndns
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/digitalocean-dyndns-0.1.4/digitalocean-dyndns-0.1.4.tgz
version: 0.1.4
frigate:
- apiVersion: v1
appVersion: 0.2.0
created: "2019-08-05T03:05:46.189367551Z"
description: Realtime object detection on RTSP cameras with the Google Coral
digest: 900de672ad5bfa77e587ad518e09950b0f44562b7fd40755256dd0c84088b2eb
home: https://github.com/billimek/billimek-charts/tree/master/frigate
icon: https://upload.wikimedia.org/wikipedia/commons/a/a4/Lutine1.jpg
keywords:
- tensorflow
- coral
- ml
maintainers:
- email: jeff@billimek.com
name: billimek
name: frigate
sources:
- https://github.com/blakeblackshear/frigate
urls:
- https://github.com/billimek/billimek-charts/releases/download/frigate-0.1.6/frigate-0.1.6.tgz
version: 0.1.6
modem-stats:
- apiVersion: v1
appVersion: 1.0.0
created: "2019-08-05T03:05:46.024450621Z"
description: periodic cable modem data collection and save the results to InfluxDB
digest: dbe15ab1e88d31dc6726ac0538982648152503dabe15c2781ac525c7b10c7ddf
home: https://github.com/billimek/billimek-charts/tree/master/modem-stats
icon: https://i.imgur.com/NprLyFf.png
keywords:
- sb6183
- influxdb
maintainers:
- email: jeff@billimek.com
name: billimek
name: modem-stats
sources:
- https://github.com/billimek/SB6183-stats-for-influxdb
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/modem-stats-1.0.6/modem-stats-1.0.6.tgz
version: 1.0.6
nzbget:
- apiVersion: v1
appVersion: v21.0-ls14
created: "2019-08-05T03:05:45.872979197Z"
description: NZBGet is a Usenet downloader client
digest: 76722584cd5a55d228d2cc68655598e8e312c24af8054ec0460fb20581c60af4
home: https://github.com/billimek/billimek-charts/tree/master/nzbget
icon: https://avatars1.githubusercontent.com/u/3368377?s=400&v=4
keywords:
- nzbget
- usenet
maintainers:
- email: jeff@billimek.com
name: billimek
name: nzbget
sources:
- https://hub.docker.com/r/linuxserver/nzbget/
- https://nzbget.net/
urls:
- https://github.com/billimek/billimek-charts/releases/download/nzbget-2.0.7/nzbget-2.0.7.tgz
version: 2.0.7
radarr:
- apiVersion: v1
appVersion: amd64-v0.2.0.1344-ls17
created: "2019-08-05T03:05:45.708619585Z"
description: Radarr is a movie downloading client
digest: ae45807488bf7e310702c7a2e98d103c951cef193834fcaf7227d9dfb3395210
home: https://github.com/billimek/billimek-charts/tree/master/radarr
icon: https://avatars3.githubusercontent.com/u/25025331?s=400&v=4
keywords:
- radarr
- usenet
- bittorrent
maintainers:
- email: jeff@billimek.com
name: billimek
name: radarr
sources:
- https://hub.docker.com/r/linuxserver/radarr/
- https://github.com/Radarr/Radarr/
urls:
- https://github.com/billimek/billimek-charts/releases/download/radarr-2.0.7/radarr-2.0.7.tgz
version: 2.0.7
rtorrent-flood:
- apiVersion: v1
appVersion: 1.0.0
created: "2019-08-05T03:05:45.600004296Z"
description: rtorrent and flood co-located in the same deployment
digest: 723279521644be2a8653cf70955c5b040301614a2a0ce65c8de059b199558f5f
home: https://github.com/billimek/billimek-charts/tree/master/rtorrent-flood
icon: https://github.com/jfurrow/flood/blob/master/flood.png?raw=true
keywords:
- rtorrent
- flood
- torrrent
maintainers:
- email: jeff@billimek.com
name: billimek
name: rtorrent-flood
sources:
- https://hub.docker.com/r/looselyrigorous/rtorrent
- https://github.com/looselyrigorous/docker-rtorrent
- https://github.com/Flood-UI/flood
- https://cloud.docker.com/repository/docker/billimek/flood
urls:
- https://github.com/billimek/billimek-charts/releases/download/rtorrent-flood-3.0.1/rtorrent-flood-3.0.1.tgz
version: 3.0.1
sonarr:
- apiVersion: v1
appVersion: amd64-2.0.0.5321-ls62
created: "2019-08-05T03:05:45.473175255Z"
description: Sonarr is a television show downloading client
digest: 96d170bcd371897dc7852dad8e3b9d6801e2f45c66ebde249534c90527ed5dbb
home: https://github.com/billimek/billimek-charts/tree/master/sonarr
icon: https://avatars1.githubusercontent.com/u/1082903?s=400&v=4
keywords:
- sonarr
- usenet
- bittorrent
maintainers:
- email: jeff@billimek.com
name: billimek
name: sonarr
sources:
- https://hub.docker.com/r/linuxserver/sonarr/
- https://sonarr.tv/
urls:
- https://github.com/billimek/billimek-charts/releases/download/sonarr-2.0.6/sonarr-2.0.6.tgz
version: 2.0.6
speedtest:
- apiVersion: v1
appVersion: 1.0.0
created: "2019-08-05T03:05:45.327612077Z"
description: periodic speedtest and save the results to InfluxDB
digest: dfd1851ea6e6903fb87ca79f8e1860bbca155e779564cdb448a2cf99becfe596
home: https://github.com/billimek/billimek-charts/tree/master/speedtest
icon: https://i.imgur.com/nDYjKk8.png
keywords:
- speedtest
- influxdb
- grafana
maintainers:
- email: jeff@billimek.com
name: billimek
name: speedtest
sources:
- https://github.com/billimek/Speedtest-for-InfluxDB-and-Grafana
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/speedtest-1.1.6/speedtest-1.1.6.tgz
version: 1.1.6
uptimerobot:
- apiVersion: v1
appVersion: 1.1.0
created: "2019-08-05T03:05:45.183229763Z"
description: A tool to get statistics from Uptime Robot and log it into InfluxDB
digest: b1ec1e86cea8dbbc3e831811c023b1effdb7adf3cd7fcd17f8f7d77b406ee1dc
home: https://github.com/billimek/billimek-charts/tree/master/uptimerobot
icon: https://i.imgur.com/ARSSILk.png
keywords:
- uptimerobot
- influxdb
- grafana
maintainers:
- email: jeff@billimek.com
name: billimek
name: uptimerobot
sources:
- https://github.com/trojanc/node-influx-uptimerobot
- https://github.com/billimek/billimek-charts
urls:
- https://github.com/billimek/billimek-charts/releases/download/uptimerobot-1.1.9/uptimerobot-1.1.9.tgz
version: 1.1.9
generated: "2019-08-05T03:05:44.566397169Z"

1
.gitignore vendored
View File

@ -1 +1,2 @@
.env
.deploy/