* [sharry] use a config blockk
* [sharry] update docs
* [sharry] use default config as example
* [sharry] comment out nginx annotations
* [sharry] fix config indentation and add base-url example
* [sharry] add bind configuration
Updated the list of ways around the host check in sabnzbd...we have a more convenient 3rd option in place already.
Signed-off-by: Branden Cash <ammmze@gmail.com>
* [comcast] migrate to common
Signed-off-by: Nicholas Wilde <ncwilde43@gmail.com>
* Remove test files. Disabled probes
Signed-off-by: Nicholas Wilde <ncwilde43@gmail.com>
* Add bookstack
Signed-off-by: Nicholas Wilde <ncwilde43@gmail.com>
* Changed version to 0.1.0
Signed-off-by: Nicholas Wilde <ncwilde43@gmail.com>
* Update README.md
* - Moved to stable
- Uncommented persistance
- Added commented DB env variables.
- Changed tag to version-v21.04.2
Signed-off-by: Nicholas Wilde <ncwilde43@gmail.com>
Co-authored-by: ᗪєνιη ᗷυнʟ <onedr0p@users.noreply.github.com>
* feat: add speedtest-exporter chart
* feat: add speedtest-exporter chart
* feat: add speedtest-exporter chart
* feat: use ghcr
* fix: remove service
* fix: remove ingress
* fix: do not enable service
* fix: use additionalPorts
* fix: use new port name
* fix: update probes
* fix: use service monitor
* fix: update port name
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* inital haste template
Signed-off-by: Ryan Walter <rwalt@pm.me>
* inital config
* removed wrong location
* renamed chart to upstream name
Signed-off-by: Ryan Walter <rwalt@pm.me>
* rebased on rwaltr/haste-server for now
* Corrected image tag and set basic storagepath
Signed-off-by: Ryan Walter <rwalt@pm.me>
* Added basic data options to values
Signed-off-by: Ryan Walter <rwalt@pm.me>
* Linting
Signed-off-by: Ryan Walter <rwalt@pm.me>
* doc regen and appversion update
Signed-off-by: Ryan Walter <rwalt@pm.me>
* dep chart Vbump
Signed-off-by: Ryan Walter <rwalt@pm.me>
* fixes#747
* fixes#747
* update docs
* use explicit name
* bump versoin, remove boolean, comment out admin env vars, and move them to the bottom so helm-docs renders properly
* use .chart.appVersion default via common so that tag is not redundant
* Update values.yaml
add back tag
* fix readme
* add initial push of jetbrains-projector
* Working version
* Update charts/stable/jetbrains-projector/README_CHANGELOG.md.gotmpl
Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <me@bjw-s.dev>
* link is totally broken
* cleanup and final push
* add a forced fail on image.repository
* add testing values
* move ct values
* fix ct test folder name
Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <me@bjw-s.dev>
* Updated intel-gpu-plugin image tag to latest stable
version upgraded from 0.19.0 to 0.20.0
* Updated chart version for intel-gpu-plugin
* Updated intel-gpu-plugin chart appVersion
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* feat: migrate adguard-home to common
* Updated AppVersion to 6.0.45
Modified the Ingress definitions to use the latest Ingress spec (networking.k8s.io/v1) for clusters 1.18+ and the beta spec (networking.k8s.io/v1beta1) 1.14+. Otherwise, continue using extensions/v1beta1
* Moved Labels and Selector Labels to _helpers (in following latest helm guidelines) and fixed ingress templates
* Modified logic in the ingress templates to reduce some of the nesting
Co-authored-by: ᗪєνιη ᗷυнʟ <onedr0p@users.noreply.github.com>
* feat!: migrate to new version on official image
* docs: example for rootless GPU transcoding
* feat!: migrate to new version on official image
* docs: example for rootless GPU transcoding
* docs: regenerate README.md
* docs: fix wording
Co-authored-by: ᗪєνιη ᗷυнʟ <onedr0p@users.noreply.github.com>
Co-authored-by: ᗪєνιη ᗷυнʟ <onedr0p@users.noreply.github.com>
* [common] Transfer to separate repo
* Remove common unittests
* Use k3d instead of kind
* Bump all charts
* Skip uninstallable charts
* [alertmanager-bot] Disable probes
* Skip uninstallable charts
* add support for an existingSecret
Signed-off-by: Ryan Holt <ryan@ryanholt.net>
* forgot the closing end
Signed-off-by: Ryan Holt <ryan@ryanholt.net>
* add a new line
Signed-off-by: Ryan Holt <ryan@ryanholt.net>
* remove serviceaccount as it serves no purpose here
* update image
* the new version no longer serves on http, it is stricrly mqtt
* sync default config with upstream
* update Readme
* bump chart
* add changelog
* port to common
* upstrema has tagged a release!
* update appVersion
* update docs
* fix configmap mount
Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <bernd@bjws.nl>
* move from customconfig to transmissionConfig
* always use transmissionConfig
* update docs
* bump chart version
* this is an incompatible change
* update docs
* [common] Allow to override container command (#499)
Signed-off-by: Ingvarr Zhmakin
Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <6213398+bjw-s@users.noreply.github.com>
* fix: add resources to values
* [common] Add support for volumeClaimTemplates in statefulset (#529)
Signed-off-by: Mikael Sennerholm <mikael@sennerholm.net>
* [common] Add support for templatified env-variables (#530)
* Add support for template env vars
Signed-off-by: Mikael Sennerholm <mikael@sennerholm.net>
* [common-next] some additional pod properties (#533)
* [common] new pod properties
* [common] Move test of statefulset (#536)
* Moved statefulset chart-test to unit test
* [common] Move env tpl test fix (#542)
* Take care of setting envTpl if no env set
* Add Test cases
* Moved to unit tests
* Update changelog, add missing fields to values
* common-test doesn't need a bump
* Relocate end statement
Co-authored-by: Ingvarr Zhmakin <19270832+lazyoldbear@users.noreply.github.com>
Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <6213398+bjw-s@users.noreply.github.com>
Co-authored-by: Mikael Sennerholm <mikael@sennerholm.net>
* Move LazyLibrarian to Common chart
Signed-off-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl>
* Update lazylibrarian to latest
- appVersion is still 1.7.2
Signed-off-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl>
* Add code-server env to values
* Bump chart version
* [common] - add ingressclass name (#441)
* add ingressclassname
Signed-off-by: Jon Baker <jonbaker85@gmail.com>
* Allow disabling of service links
* Update changelog
* Update changelog
* Set better default for targetPort
* Allow for different container / service ports
* Fix linting error
* Add unit tests
* Add unit tests
* Add unit tests
* Service unit tests
* Split CI jobs
* Testing CI
* Testing CI
* Testing CI
* Testing CI
* Rename test file to match source
* Fix newline
Co-authored-by: Jon Baker <jonbaker85@gmail.com>
Co-authored-by: ᗪєνιη ᗷυнʟ <onedr0p@users.noreply.github.com>
- Bring `appVersion` from `Chart.yaml` back in sync with the wq`image.tag` from `values.yaml`
- `postgres.enabled` -> `postgresql.enabled` for postgresql dependency in `Chart.yaml`
Signed-off-by: David Armstrong <stretched@users.noreply.github.com>
* [blocky] add query log persistence
Signed-off-by: Adam Cook <adam@adamjcook.dev>
* [blocky] bump version to v0.11
Signed-off-by: Adam Cook <adam@adamjcook.dev>
* Add jvmInitHeapSize and jvmMaxHeapSize which are passed on
to the container as env vars
* Bump version, no change in default behaviour
* Update README.md with new configuration parameters
Signed-off-by: Thomas Ingvarsson <ingvarsson.thomas@gmail.com>
* Parameterize timing of livenessProbe
* Parameterize timing of readinessProbe
* Bump version, no change in default behaviour
* Update README.md with new configuration parameters
Signed-off-by: Thomas Ingvarsson <ingvarsson.thomas@gmail.com>
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* Add startupProbe to Node-RED chart in order to address slow starting container being killed due to liveness probe failures.
* Bump node-red chart version
* Add hostAliases support for custom /etc/hosts entries
* Update description for hostAliases
* Add startupProbe to Node-RED chart in order to address slow starting container being killed due to liveness probe failures.
* Bump node-red chart version
* Update version to reflect new feature.
* Paramaterisation of liveness, readiness and startup probe configuration.
Configure startup probe to disabled by default.
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* bump chart version
* [uptimerobot-prometheus] Support annotations in Service (#1)
* add annotations to service
* add example annotations to values.yaml
* fix trailing spaces
* Added ability to control vscode arguments
Signed-off-by: Richard Cox <cox.richard200@gmail.com>
* Fixed helpers function to handle null and empty string vscode.args value
Signed-off-by: Richard Cox <cox.richard200@gmail.com>
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* Added the ability to specify subPaths
I mount all my configs into a volume and keep each app under subPaths. By adding the ability of specifying a subpath here I can set hass to store its settings on its own folder.
thanks
* Update Chart.yaml
Version bumped
* Update deployment.yaml
Fixed a typo, the here the config sub path is for appdaemon and not vscode
* Update README.md
Added the new variables to the table
* Update README.md
Removed the git configSubPath because is the same as configSubPath. Same mount definition as the hass config. Also moved the configSubPath setting under persistence which makes more sense
* Update deployment.yaml
Changed configSubPath to be under persistence. Unified the git.configSubPath with the persistence one as they are the same.
* Update values.yaml
Added configSubPath to the values.yaml with a comment.
* Update Chart.yaml
Version bump
* Update values.yaml
trailing space... come on github editor you failed me
* Update values.yaml
Added the subpath setting under appDaemon
* Update values.yaml
trailing spaces... github editor needs an update
* Update values.yaml
grrr trailing spaces
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* [homebridge] New chart
* [homebridge] Additional variables in README
* [homebridge] Set default service type to ClusterIP
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* Added option to specify ServiceAccount (needed to associate a PodSecurityPolicy)
* Bumped chart version, added variable to README
* Bumped version to 3.1.0, as per request
* [nzbget] Migrate to media-common
* [nzbget] Migrate to media-common
* [nzbget] Fix indenting in values
Co-authored-by: Jeff Billimek <jeff@billimek.com>
* Fix name of cert secret
The original name in the documentation is incorrect.
Signed-off-by: Matt Farmer <matt@frmr.me>
* Increment patch number
Signed-off-by: Matt Farmer <matt@frmr.me>
* Correctly bump unifi chart version
Signed-off-by: Matt Farmer <matt@frmr.me>
* [stable/unifi] adding functionality to mount extra volumes
This change adds possibility to specify additional volumes
when deploying Unifi controller.
Signed-off-by: Marcin Iwinski <marcin.iwinski@gmail.com>
* fixing defaults in README.md
Signed-off-by: Marcin Iwinski <marcin.iwinski@gmail.com>
* [stable/unifi] bumping version to 0.9.0
Signed-off-by: Marcin Iwinski <marcin.iwinski@gmail.com>
Adding possibility to expose certificate and its key via k8s secret/tls.
Since secret/tls keeps cert under tls.crt and key under tls.key modified
default values for customCert.certName and customCert.keyName to be
more compatible with k8s native way of storing certificates.
Signed-off-by: Marcin Iwinski <marcin.iwinski@gmail.com>
* unifi chart supports subPath for existing PVCs
Signed-off-by: James Choncholas <jchoncholas@gmail.com>
* bump version number
Signed-off-by: James Choncholas <jchoncholas@gmail.com>
* bump the unifi docker image to version 5.11.50
* forward port values to unifi docker environment variables
Closes#18051
Signed-off-by: Per Otterström <per.otterstrom@gmail.com>
* Fix unifi NOTES to find correct service
Unifi installs the gui service as unifi-gui, but the command in the notes points to a non-existent 'unifi' service. Use unifi.name + '-gui' to construct the service name here which duplicates the logic in gui-svc.yaml.
Signed-off-by: Brian Johnson <brian@sherbang.com>
* Increment unifi version to 0.4.2
Signed-off-by: Brian Johnson <brian@sherbang.com>
* switching unifi chart to SatefulSet
* based on the persistent nature of this chart as well as [this
discussion](https://github.com/helm/charts/issues/1863), migrating the
chart to a StatefulSet instead of a deployment. As a result bumping the
major version
* bumping unifi controller to the latest stable version (5.10.19)
* adding @mcronce to the OWNERS file
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* using volumeClaimTemplates for statefulSet
* also updating label syntax to current helm standards (e.g.
`app.kubernetes.io/name`)
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* fixing indenting
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* using Parallel podManagementPolicy
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* revert to Deployment and leverage strategy types
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* include readme entry for strategyType
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* hard-code replica count and add mcronce to Chart maintainers
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* fixing linting error
Signed-off-by: Jeff Billimek <jeff@billimek.com>
.Values was out of scope for hosts block, since its in a range statement
Moved the failing access to unifiedService.enabled to a variable
Signed-off-by: Thiemo Krause <krausethiemo@googlemail.com>
* Revert "Simplify for unifi (#10789)"
This reverts commit b09535dfb4.
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* bumping chart version as part of reversion
Signed-off-by: Jeff Billimek <jeff@billimek.com>
The discovery and stun ports are part of the same service. Unifi depends
on them to be on the same hostname.
Signed-off-by: Werner Buck <email@wernerbuck.nl>
If you do a port-forward to 8080, the unifi controller tries to forward you to a secure TLS connection on port 8443. This fails because the port 8443 is not forwarded. If you do a direct forward to 8443, everything works as expected.
Signed-off-by: Christian Erhardt <christian.erhardt@mojo2k.de>
Use case is using `ark` + `restic` to take backups which requires pods
with persistent data to be annotated like:
```
kubectl annotate pod unifi-55f6dcc44c-khbrk backup.ark.heptio.com/backup-volumes=unifi-data
```
Signed-off-by: Lyle Franklin <lylejfranklin@gmail.com>
* stable/unifi/templates/deployment.yaml: fix probes
The `livenessProbe` and `readinessProbe` are incorrectly defined.
The `initialDelaySeconds` field should not be nested withing the `httpGet`
field.
Signed-off-by: Lucas Serven <lserven@gmail.com>
* stable/unifi: bump patch version
Signed-off-by: Lucas Serven <lserven@gmail.com>
* Invalid link in chart sources
There was a invalid link in sources, this commit fixes the link
Signed-off-by: Jonathan Herlin <jonte@jherlin.se>
* stable/unifi bump version
Signed-off-by: Jonathan Herlin <jonte@jherlin.se>
* initial commit - unifi controller chart
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* enabling persistence by default, per guidelines
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* enabling persistence by default, per guidelines
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* changes requested in PR
* Pegging to a certain version for the chart (0.1.0) until otherwise directed
* Using consistent indentation for lists
* Using camelCase
* updating app version to current (5.8.28)
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* correcting linting failures
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* adding OWNERS for more timely merges in the future
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* Correcting inconsistent service definitions
* fixing inconsistencies with service port & name definitions as described in PR
* bumping app version to current
* correcting typo in Charts.yaml
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* correcting ingress servicePort definition
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* correcting ingress servicePort definition
Signed-off-by: Jeff Billimek <jeff@billimek.com>
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* adding missing NodePort settings
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* Expanding service definitions
* The values and readme reflect that the various services (deployment, stun, gui, controller) can handle annotations, but there is no use of those in the templates. This is now fixed
* Added externalTrafficPolicy to all services
* Some of these changes were requested via https://github.com/billimek/billimek-charts/issues/3
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* switching to apps/v1
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* mass-rename of chart repo
* update all Chart.yaml files to replace references from old repo to new
repo
* update all Chart.yaml files to set apiVersion to v2 where necessary
* update all README.md files to replace references from old repo to new
repo
* fix teslamate dependencies for v2
Signed-off-by: Jeff Billimek <jeff@billimek.com>
Before you open the request please review the following guidelines and tips to help it be more easily integrated:
#### Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
-[ ] Chart Version bumped
- [ ] Variables are documented in the README.md
- [ ] Title of the PR starts with chart name (e.g. `[radarr]`)
- Describe the scope of your change - i.e. what the change does.
- Describe any known limitations with your change.
- Please run any tests or examples that can exercise your modified code.
Thank you for contributing! We will try to test and integrate the change as soon as we can. There is no need to bump or check in on a pull request (it will clutter the discussion of the request).
Also don't be worried if the request is closed or not integrated sometimes our priorities might not match the priorities of the pull request. Don't fret, the open source community thrives on forks and GitHub makes it easy to keep your changes in a forked repo.
-->
**Description of the change**
<!-- Describe the scope of your change - i.e. what the change does. -->
**Benefits**
<!-- What benefits will be realized by the code change? -->
**Possible drawbacks**
<!-- Describe any known limitations with your change -->
**Applicable issues**
<!-- Enter any applicable Issues here (You can reference an issue using #) -->
- fixes #
**Additional information**
<!-- If there's anything else that's important and relevant to your pull request, mention that information here.-->
**Checklist** <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
- [ ] Chart version bumped in `Chart.yaml` according to [semver](http://semver.org/).
- [ ] Title of the PR starts with chart name (e.g. `[home-assistant]`)
- [ ] Variables are documented in the README.md (this can be done with using our helm-docs wrapper `./hack/gen-helm-docs.sh stable <chart>`)
<!-- Keep in mind that if you are submitting a new chart, try to use our [common](https://github.com/k8s-at-home/charts/tree/master/charts/common) library as a dependency. This will help maintaining charts here and keep them consistent between each other -->
# Configuration for probot-stale - https://github.com/probot/stale
# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale:45
# Number of days of inactivity before a stale Issue or Pull Request is closed.
daysUntilClose:5
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
- on-hold
- pinned
# Label to use when marking as stale
staleLabel:stale
issues:
# Comment to post when marking as stale. Set to `false` to disable
markComment:>
This Issue has been automatically marked as "stale" because it has not had recent activity (for 45 days). It will be closed if no further activity occurs. Thanks for the feedback.
# Comment to post when closing a stale Issue or Pull Request.
closeComment:>
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
pulls:
# Comment to post when marking as stale. Set to `false` to disable
markComment:>
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 45 days). It will be closed if no further activity occurs. Thank you for your contribution.
# Comment to post when closing a stale Issue or Pull Request.
closeComment:>
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.
# Limit the number of actions per hour, from 1-30. Default is 30
* Must follow [Charts best practices](https://helm.sh/docs/topics/chart_best_practices/)
* Must pass CI jobs for linting and installing changed charts with the [chart-testing](https://github.com/helm/chart-testing) tool
* Any change to a chart requires a version bump following [semver](https://semver.org/) principles. See [Immutability(#immutability) and [Versioning](#versioning) below
* Must follow [Charts best practices](https://helm.sh/docs/topics/chart_best_practices/).
* Must pass CI jobs for linting and installing changed charts with the [chart-testing](https://github.com/helm/chart-testing) tool See [pre-commit](#pre-commit) below.
* Any change to a chart requires a version bump following [semver](https://semver.org/) principles. See [Immutability](#immutability) and [Versioning](#versioning) below.
Once changes have been merged, the release job will automatically run to package and release changed charts.
@@ -51,3 +51,7 @@ Charts should start at `1.0.0`. Any breaking (backwards incompatible) changes to
1. Bump the MAJOR version
2. In the README, under a section called "Upgrading", describe the manual steps necessary to upgrade to the new (specified) MAJOR version
### Pre-commit
This repo supports the [pre-commit](https://pre-commit.com) framework. By installing the framework (see [docs](https://pre-commit.com/#install)) it is possible to perform the chart linting step before committing your code. This can help prevent linter issues in the pipeline. Note that this requires having Docker running on your development environment.
- Bugs or feature requests should be opened in an [issue](https://github.com/k8s-at-home/charts/issues/new/choose).
- Questions or comments should be discussed in our [Discord](https://discord.gg/sTMX7Vh) or via [Github discussions](https://github.com/k8s-at-home/organization/discussions).
## Contributing
@@ -27,3 +37,51 @@ See [CONTRIBUTING.md](./CONTRIBUTING.md)
## License
[Apache 2.0 License](./LICENSE)
## Contributors ✨
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
To uninstall/delete the `adguard-home` deployment:
```console
helm delete adguard-home --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/charts/adguard-home/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 adguard-home \
--set timeZone="America/New York" \
billimek/adguard-home
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
This is a helm chart for [bazarr](https://github.com/morpheus65535/bazarr) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/bazarr)
To install the chart with the release name `my-release`:
```console
helm install --name my-release billimek/bazarr
```
## Upgrading
Version 1.0.0 used separate PVCs for TV and Movies. In order to keep this chart inline
with changes to charts for Sonarr, etc. this was changed.
This chart now uses a single PVC for all media. This means all of your media must be in, or be subdirectories of, a single media directory. If upgrading from v1 of the chart, do the following:
1. [Uninstall](#uninstalling-the-chart) your current release
2. On your backing store, organize your media, ie. media/tv, media/movies
3. If using a pre-existing PVC, create a single new PVC for all of your media
4. Refer to the [configuration](#configuration) for updates to the chart values
5. Re-install the chart
6. Update your settings in the app to point to the new PVC, which is mounted at /media. These can be found at: `Settings -> Path Mappings For TV Shows` and `Settings -> Path Mappings for Movies`
## 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.
If you get `Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...` it may be because you uninstalled the chart with `skipuninstall` enabled, you need to manually delete the pvc or use `existingClaim`.
---
Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/charts/bazarr/values.yaml) file. It has several commented out suggested values.
To install the chart with the release name `bitwarden`:
```console
helm install bitwarden billimek/bitwardenrs
```
## Uninstalling the Chart
To uninstall/delete the `bitwarden` deployment:
```console
helm uninstall bitwarden
```
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/charts/bitwardenrs/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 bitwarden \
--set timeZone="America/New York" \
billimek/bitwardenrs
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
To install the chart with the release name `my-release`:
```console
helm install --name blocky billimek/blocky
```
## Uninstalling the Chart
To uninstall/delete the `blocky` deployment:
```console
helm delete blocky --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/charts/blocky/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 blocky \
--set timeZone="America/New York" \
billimek/blocky
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
# blocky configuration - will translate to config.yml file inside the pod
config:
upstream:
# these external DNS resolvers will be used. Blocky picks 2 random resolvers from the list for each query
# format for resolver: net:host:[port][/path]. net could be tcp, udp, tcp-tls or https (DoH). If port is empty, default port will be used (53 for udp and tcp, 853 for tcp-tls, 443 for https (Doh))
externalResolvers:
- udp:8.8.8.8
- udp:8.8.4.4
- udp:1.1.1.1
- tcp-tls:1.0.0.1:853
- https://cloudflare-dns.com/dns-query
# optional: custom IP address for domain name (with all sub-domains)
# example: query "printer.lan" or "my.printer.lan" will return 192.168.178.3
# customDNS:
# mapping:
# printer.lan: 192.168.178.3
# optional: definition, which DNS resolver should be used for queries to the domain (with all sub-domains).
# Example: Query client.fritz.box will ask DNS server 192.168.178.1. This is necessary for local network, to resolve clients by host name
# conditional:
# mapping:
# fritz.box: udp:192.168.178.1
# optional: use black and white lists to block queries (for example ads, trackers, adult pages etc.)
blocking:
# definition of blacklist groups. Can be external link (http/https) or local file
This is a helm chart for [calibre-web](https://github.com/janeczku/calibre-web) utilizing the [Linuxserver.io calibre-web image](https://hub.docker.com/r/linuxserver/calibre-web)
| `dockerMods.ebookConversion.image.tag` | DockerMod image tag. These typically start with `v`, with the "stable" tag being `calibre`. Can be found [here](https://hub.docker.com/r/linuxserver/calibre-web/tags/) | `calibre` |
| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` |
| `timezone` | Timezone the calibre-web instance should run as, e.g. 'America/New_York' | `UTC` |
| `puid` | process userID the calibre-web instance should run as | `1001` |
| `pgid` | process groupID the calibre-web instance should run as | `1001` |
| `umask` | Default umask to use when creating new files | `22` |
| `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 calibre-web GUI | `ClusterIP` |
| `Service.port` | Kubernetes port where the calibre-web GUI is exposed | `8083` |
| `Service.annotations` | Service annotations for the calibre-web GUI | `{}` |
| `Service.labels` | Custom labels | `{}` |
| `Service.loadBalancerIP` | Loadbalance IP for the calibre-web GUI | `{}` |
| `Service.loadBalancerSourceRanges` | List of IP CIDRs allowed access to load balancer (if supported) | None |
If you get `Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...` it may be because you uninstalled the chart with `skipuninstall` enabled, you need to manually delete the pvc or use `existingClaim`.
---
Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/charts/calibre-web/values.yaml) file. It has several commented out suggested values.
{{- if .Values.dockerMods.ebookConversion.enabled }}
2. DockerMods:
You have enabled the EbookConversion Docker Mod using the {{ .Values.dockerMods.ebookConversion.image.repository }}:{{ .Values.dockerMods.ebookConversion.image.tag }} image.
Remember to visit https://github.com/linuxserver/docker-calibre-web#application-setup for instructions on configuring this feature in the calibre-web settings.
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.
Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/charts/comcast/values.yaml) file. It has several commented out suggested values.
This is a helm chart for [couchpotato](https://github.com/couchpotato/couchpotato/) leveraging the [Linuxserver.io image](https://hub.docker.com/r/linuxserver/couchpotato/)
If you get `Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...` it may be because you uninstalled the chart with `skipuninstall` enabled, you need to manually delete the pvc or use `existingClaim`.
---
Read through the [values.yaml](https://github.com/billimek/billimek-charts/blob/master/charts/couchpotato/values.yaml) file. It has several commented out suggested values.
{{- else if contains "ClusterIP" .Values.service.type }}
export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "couchpotato.name" . }},app.kubernetes.io/instance={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl port-forward $POD_NAME 8080:5050
{{- end }}
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.