pascaliske / helm-charts Goto Github PK
View Code? Open in Web Editor NEWAnother repository with lightweight Helm Charts.
Home Page: https://charts.pascaliske.dev
License: MIT License
Another repository with lightweight Helm Charts.
Home Page: https://charts.pascaliske.dev
License: MIT License
I just upgraded to the latest version of the chart, and noticed that DNS via TCP was no longer working.
$ dig @192.168.99.166 suse.de +tcp
;; Connection to 192.168.99.166#53(192.168.99.166) for suse.de failed: connection refused.
Editing the service and changing targetPort: dns-tcp
to targetPort: 5053
immediately restores the connectivity.
Funnily enough, for dns-udp it is working even with the name for the targetPort... :-)
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
.github/workflows/labels.yml
actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
crazy-max/ghaction-github-labeler v5
.github/workflows/release.yml
actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
azure/setup-helm v3.5
arduino/setup-task v1
actions/cache v4
helm/chart-releaser-action v1.6.0
.github/workflows/test.yml
actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
actions/setup-python v5
azure/setup-helm v3.5
helm/chart-testing-action v2.6.1
helm/kind-action v1.10.0
charts/clickhouse/values.yaml
charts/cloudflare-dyndns/values.yaml
charts/cloudflared/values.yaml
charts/code-server/values.yaml
charts/ctfd/values.yaml
charts/digitalocean-dyndns/values.yaml
charts/fritzbox-exporter/values.yaml
charts/gitlab/values.yaml
charts/hammond/values.yaml
charts/homer/values.yaml
charts/keycloak/values.yaml
charts/linkding/values.yaml
charts/paperless/values.yaml
charts/plausible-exporter/values.yaml
charts/plausible/values.yaml
ghcr.io/maxmind/geoipupdate v7.0.1
charts/redis/values.yaml
charts/snapdrop/values.yaml
charts/traefik-errors/values.yaml
charts/unbound/values.yaml
charts/uptime-kuma/values.yaml
charts/vaultwarden/values.yaml
charts/vikunja/values.yaml
charts/clickhouse/Chart.yaml
base 1.2.0
charts/cloudflared/Chart.yaml
base 1.2.0
charts/code-server/Chart.yaml
base 1.2.0
charts/ctfd/Chart.yaml
base 1.2.0
charts/fritzbox-exporter/Chart.yaml
base 1.2.0
charts/gitlab/Chart.yaml
base 1.2.0
charts/hammond/Chart.yaml
base 1.2.0
charts/homer/Chart.yaml
base 1.2.0
charts/keycloak/Chart.yaml
base 1.2.0
charts/linkding/Chart.yaml
base 1.2.0
charts/paperless/Chart.yaml
base 1.2.0
redis 1.4.0
charts/plausible-exporter/Chart.yaml
base 1.2.0
charts/plausible/Chart.yaml
base 1.2.0
charts/redis/Chart.yaml
base 1.2.0
charts/snapdrop/Chart.yaml
base 1.2.0
charts/traefik-errors/Chart.yaml
base 1.2.0
charts/unbound/Chart.yaml
base 1.2.0
charts/uptime-kuma/Chart.yaml
base 1.2.0
charts/vaultwarden/Chart.yaml
base 1.2.0
charts/vikunja/Chart.yaml
base 1.2.0
package.json
@commitlint/cli ^19.0.0
@commitlint/config-conventional ^19.0.0
husky ^9.0.0
lint-staged ^15.0.0
yarn 1.22.22
docs/requirements.txt
material-plausible-plugin ==0.2.0
charts/clickhouse/Chart.yaml
clickhouse/clickhouse-server 24.7.2.13-alpine
charts/cloudflare-dyndns/Chart.yaml
ghcr.io/pascaliske/cloudflare-dyndns 0.1.1
charts/cloudflared/Chart.yaml
ghcr.io/crazy-max/cloudflared 2024.6.1
charts/code-server/Chart.yaml
ghcr.io/coder/code-server 4.91.1
charts/ctfd/Chart.yaml
ghcr.io/ctfd/ctfd 3.7.3
charts/digitalocean-dyndns/Chart.yaml
ghcr.io/pascaliske/digitalocean-dyndns 0.0.3
charts/fritzbox-exporter/Chart.yaml
sealife/fritzbox-exporter 1.0
charts/gitlab/Chart.yaml
gitlab/gitlab-ce 17.2.1-ce.0
charts/hammond/Chart.yaml
ghcr.io/alfhou/hammond v0.0.24
charts/homer/Chart.yaml
ghcr.io/bastienwirtz/homer v24.05.1
charts/keycloak/Chart.yaml
quay.io/keycloak/keycloak 25.0.2
charts/linkding/Chart.yaml
sissbruecker/linkding 1.31.0
charts/paperless/Chart.yaml
ghcr.io/paperless-ngx/paperless-ngx 2.11.2
charts/plausible-exporter/Chart.yaml
ghcr.io/riesinger/plausible-exporter 1.1.0
charts/plausible/Chart.yaml
plausible/analytics v2.0.0
charts/redis/Chart.yaml
redis 7.4.0
charts/snapdrop/Chart.yaml
charts/traefik-errors/Chart.yaml
ghcr.io/pascaliske/traefik-errors 1.2.0
charts/unbound/Chart.yaml
ghcr.io/pascaliske/unbound 0.1.0
charts/uptime-kuma/Chart.yaml
louislam/uptime-kuma 1.23.13
charts/vaultwarden/Chart.yaml
ghcr.io/dani-garcia/vaultwarden 1.32.0
charts/vikunja/Chart.yaml
vikunja/vikunja 0.24.1
Is the repo link still valid?
I'm getting the following error -
$ helm repo add pascaliske https://charts.pascaliske.dev
Error: looks like "https://charts.pascaliske.dev" is not a valid chart repository or cannot be reached: failed to fetch https://charts.pascaliske.dev/index.yaml : 503 Service Unavailable
is it just me ?
Is your feature request related to a problem? Please describe.
If the chart index on the gh-pages branch gets corrupted the chart-release workflow can not restore it.
Describe the solution you'd like
Create a workflow to rebuild the index if it got corrupted.
Describe alternatives you've considered
Update the chart index in an idempotent fashion during the release process.
Additional context
** (RuntimeError) BASE_URL configuration option is required. See https://plausible.io/docs/self-hosting-configuration#server
** (RuntimeError) SECRET_KEY_BASE configuration option is required. See https://plausible.io/docs/self-hosting-configuration#server
https://github.com/pascaliske/helm-charts/actions/runs/4439709035/jobs/7792548732#step:9:1
Is your feature request related to a problem? Please describe.
The consumption, export and trash directories currently only allow to be mounted to host paths:
consumption:
# -- Enable the volume mount of a [consumption directory](https://paperless-ngx.readthedocs.io/en/latest/configuration.html#paths-and-folders).
enabled: false
# -- Mount path of the consumption directory inside the container.
mountPath: /consumption
# -- Host path of the consumption directory outside the container.
hostPath: ''
This is not practical for Kubernetes because when using NAS etc. for backups, the directories first need to be mounted on all nodes.
Describe the solution you'd like
I would like an option to specify an existing PVC to mount these at, like:
consumption:
# -- Enable the volume mount of a [consumption directory](https://paperless-ngx.readthedocs.io/en/latest/configuration.html#paths-and-folders).
enabled: true
# -- Mount path of the consumption directory inside the container.
mountPath: /consumption
# -- Host path of the consumption directory outside the container.
hostPath: ''
# -- PVC of the consumption directory
persistentVolumeClaim: 'my-consumption-claim'
Describe alternatives you've considered
Using some automation technology (like Ansible) to mount the directory to each node, but this opposes the idea of Kubernetes.
@default
comments for image tagsappVersion
updatesHi Pascal,
helm-charts/charts/paperless/values.yaml
Line 88 in 03a9a43
I am currently trying to setup paperless. I have a secret that contains the keys as stated a little below:
[...]
stringData:
PAPERLESS_SECRET_KEY: ADD-A-RANDOM-STRING-HERE
PAPERLESS_ADMIN_USER: YOUR-USERNAME-GOES-HERE
PAPERLESS_ADMIN_PASSWORD: YOUR-PASSWORD-GOES-HERE
PAPERLESS_ADMIN_MAIL: YOUR-MAIL-ADDRESS-GOES-HERE
PAPERLESS_URL: YOUR-URL-GOES-HERE
However it seems like the chart only uses the PAPERLESS_SECRET_KEY
from the existing secret:
$ kubectl get deploy paperless
[...]
spec:
containers:
- env:
- name: TZ
value: UTC
- name: PAPERLESS_TIME_ZONE
value: UTC
- name: PAPERLESS_CONSUMPTION_DIR
value: /consumption
- name: PAPERLESS_REDIS
value: redis://paperless-redis:6379
- name: PAPERLESS_SECRET_KEY
valueFrom:
secretKeyRef:
key: PAPERLESS_SECRET_KEY
name: paperless-admin
- name: PAPERLESS_PORT
value: "8000"
[...]
Should this be working? Am I missing something?
Unfortunately this chart does not have a envFrom:
, at least according to the values.yaml.
Is your feature request related to a problem? Please describe.
Running the chart directly does not set admin user / password so no login is possible.
Describe the solution you'd like
Add a configuration option to the values.yaml
that either creates a new secret or allows to use an existing one to set the admin credentials.
Describe alternatives you've considered
As a workaround, it is possible to set the credentials using the environment variables PAPERLESS_ADMIN_USERNAME
and PAPERLESS_ADMIN_PASSWORD
.
I installed the paperless-ngx chart and can't login. admin:admin
does not work and I don't find any secret with the credentials. What are the default ones?
Is your feature request related to a problem? Please describe.
It should be possible to enable support for MaxMinds GeoLite2 DB through a flag.
Describe the solution you'd like
The flag enables the deployment of the official image maxmindinc/geoipupdate
as a sidecar container for Plausible.
Describe alternatives you've considered
Additional context
Describe the bug
I'm a beginner with helm so I might be doing something wrong, but after deploying the paperless-ngx chart with redis enabled, the pod fails to start with the following error:
Adjusting permissions of paperless files. This may take a while.
Waiting for Redis...
Redis ping #0 failed.
Error: Error 111 connecting to localhost:6379. Connection refused..
Waiting 5s
Redis ping #1 failed.
Error: Error 111 connecting to localhost:6379. Connection refused..
Waiting 5s
Redis ping #2 failed.
Error: Error 111 connecting to localhost:6379. Connection refused..
Waiting 5s
Redis ping #3 failed.
Error: Error 111 connecting to localhost:6379. Connection refused..
Waiting 5s
Redis ping #4 failed.
Error: Error 111 connecting to localhost:6379. Connection refused..
Waiting 5s
Failed to connect to redis using environment variable PAPERLESS_REDIS.
To me it seems like you added the variable to your CI dir so it can pass tests, but in my opinion it should have been present in the template, within an if
block. This would also allow proper injection of redis' service name.
To Reproduce
Steps to reproduce the behavior:
Deploy the paperless chart with the following values:
redis:
enabled: true
Expected behavior
The PAPERLESS_REDIS variable gets properly set with the generated (or overwritten) redis service name
If I set the following configuration, the chart creates a pvc even though there is an existingPersistentVolumeClaim configured:
persistentVolumeClaim:
create: false
existingPersistentVolumeClaim: "smb-pvc-container-paperless-data"
This creates the following unnecessary pvc:
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
app.kubernetes.io/instance: paperless
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: paperless
app.kubernetes.io/version: 2.4.3
helm.sh/chart: paperless-5.1.0
name: paperless-storage
namespace: paper
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
volumeMode: Filesystem
I would expect, if create: false, the pvc wouldn't be created and only the pvc from existingPersistentVolumeClaim used.
The chart doesn't use the volume from the created pvc but the existing pvc from existingPersistentVolumeClaim.
So a complete useless pvc and pv are getting created.
See here: badges/shields#8671
Describe the solution you'd like
Newer Kubernetes versions allow combining TCP & UDP ports to be combined into a single service. This should be optionally possible with this chart.
I tried to upgrade from chart version 0.3.1
to the latest 1.0.5
(at the time of writing) and it failed with the error: reconciliation failed: Helm upgrade failed: cannot patch "linkding" with kind Deployment: Deployment.apps "linkding" is invalid: spec.template.spec.containers[0].volumeMounts[0].name: Not found: "storage-volume"
I have a pre-baked PV and PVC that I refer to and they've worked quite well so far.
---
kind: PersistentVolume
apiVersion: v1
metadata:
name: storage-volume
spec:
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Retain
storageClassName: local-path
local:
path: /home/....
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: storage-volume
namespace: linkding
spec:
accessModes:
- ReadWriteOnce
storageClassName: local-path
resources:
storage: 10Gi
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
name: pascaliske
namespace: linkding
spec:
interval: 60m
url: https://charts.pascaliske.dev
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: linkding
namespace: linkding
spec:
interval: 30s
chart:
spec:
chart: linkding
version: "0.3.1" # <- I only changed this line to 1.0.5
sourceRef:
kind: HelmRepository
name: pascaliske
namespace: linkding
interval: 60m
values:
persistentVolumeClaim:
create: false
existingPersistentVolumeClaim: storage-volume
---
The cluster is managed with FluxCD, hence the HelmRepository
and HelmRelease
objects. What I saw among the k8s events was the Helm release tried to provision another volume, named linkding-storage
and disregarded my pre-made PV and PVC although they were there and named exactly as the release required. Any pointer would be greatly appreciated.
I am running the service with type Loadbalancer
on my local k3s+MetalLB cluster.
However, after enabling the metrics, I cannot upgrade as mixed protocols are not allowed on services of type Loadbalancer
.
Error: UPGRADE FAILED: cannot patch "cloudflared" with kind Service: Service "cloudflared" is invalid: spec.ports: Invalid value: []core.ServicePort{core.ServicePort{Name:"dns", Protocol:"UDP", AppProtocol:(*string)(nil), Port:53, TargetPort:intstr.IntOrString{Type:0, IntVal:5053, StrVal:""}, NodePort:30686}, core.ServicePort{Name:"metrics", Protocol:"TCP", AppProtocol:(*string)(nil), Port:49312, TargetPort:intstr.IntOrString{Type:0, IntVal:5053, StrVal:""}, NodePort:0}}: may not contain more than 1 protocol when type is 'LoadBalancer'
I can think of two solutions:
Is your feature request related to a problem? Please describe.
I would like to share a PVC between clickhouse and postgres (as dependencies of plausible). For that I'm interested in splitting each DB volume path under their own directory
Describe the solution you'd like
{{- if eq (include "base.persistence.enabled" . ) "true" }}
- name: {{ include "base.persistence.suffix" (include "clickhouse.fullname" . ) }}
mountPath: {{ .Values.persistentVolumeClaim.mountPath }}
--> subPath: {{ .Values.persistentVolumeClaim.subPath }}
{{- end }}
with .Values.persistentVolumeClaim.subPath: "" in values.yaml
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/#volumemount-v1-core
Describe alternatives you've considered
2 PVCs
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.