djjudas21
commented
1 year ago Hey, thanks for reporting and sorry to hear you didn't get this working. These charts are supposed to good enough for other people to use, although it's only me who maintains them.
Let me share with you the exact values that I use to deploy with this chart:
env:
# -- Set the container timezone
TZ: Europe/London
# -- joplin-server base URL
APP_BASE_URL: https://joplin.myserver.com
# -- joplin-server listening port (same as Service port)
APP_PORT: 22300
# -- Use pg for postgres
DB_CLIENT: pg
# -- Postgres DB Host
POSTGRES_HOST: joplin-server-postgresql
# -- Postgres DB port
POSTGRES_PORT: # 5432
# -- Postgres DB name
POSTGRES_DATABASE: joplin
# -- Postgres DB Username
POSTGRES_USER: joplin
# -- Postgres DB password
POSTGRES_PASSWORD: joplin-pass
controller:
replicas: 2
affinity:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
podAffinityTerm:
labelSelector:
matchExpressions:
- key: app.kubernetes.io
operator: In
values:
- joplin-server
topologyKey: kubernetes.io/hostname
resources:
requests:
cpu: 10m
memory: 192Mi
ingress:
main:
enabled: true
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
ingressClassName: "public"
hosts:
- host: joplin.myserver.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: ingress-tls
hosts:
- joplin.myserver.com
# -- Enable and configure postgresql database subchart under this key.
# For more options see [postgresql chart documentation](https://github.com/bitnami/charts/tree/master/bitnami/postgresql)
postgresql:
enabled: true
auth:
postgresPassword: joplin-admin-pass
username: joplin
password: joplin-pass
database: joplin
primary:
persistence:
enabled: true
retain: true
storageClass: cstor
size: 2Gi
resources:
limits: {}
requests:
memory: 64Mi
cpu: 10m
priorityClassName: databaseThere's a lot of stuff in my example that isn't exactly necessary (like running 2 replicas on different nodes) but I think the key to your problem is probably in the environment variables and the postgres credentials. Can you retry, explicitly setting the POSTGRES_ env vars, and the postgresql.auth config?
In the default values.yaml for this chart, those env vars are empty. It's tricky, because you do need to manually set the POSTGRES_ variables, so ideally they could be set by default. But, you can't assume that an end user wants to deploy postgres as part of the chart. So it's kind of broken both ways unless you explicitly set some options.
Let me know if you get this working with the extra options, and let me have a think about making this chart work out of the box so it's a better experience for everyone.
zorbathut
Is your feature request related to a problem ?
I recently tried to get the Joplin Server Helm chart working. I was not successful; I managed to get a whole bunch of 404 errors and not a lot more, despite gradually maneuvering my way through tricky k8s-at-home errors and doing a whole bunch of tweaking.
I eventually gave up and scrapped the Helm chart and just did it in straight k8s.
Describe the solution you'd like.
I don't know if this is intended for end-users to use or if it's just personal. If it's just personal, rock on, you do you :) but if it's intended for end-users, a working example deployment would be nice! For Joplin Server specifically, there's a few settings that absolutely need to be changed, and it's unclear how to get the ingress working correctly.
Describe alternatives you've considered.
[none]
Additional context.
Here's the Helmfile I ended up with, which didn't work:
I have no idea how close I was.