inspired by rss-is-dead.lol, i decided to start self-hosting an RSS reader. the one i deployed is Miniflux, “a minimalist and opinionated feed reader”. it’s not clear to me what its opinions are, but i do like the simple pinboardesque interface.
i deployed it using the Helm chart provided by Gabe365. this chart
seems to be part of the splintering of k8s-at-home
. it does the trick, but i had to
work around a few issues:
- ingress configuration is unusual; especially i had to explictly provide a
seceretName
totls
configuration. - getting postgres configured without including the password in
values.yaml
was a little challenging. i had to useexistingSecret
(which is supported by the upstream bitnami chart), but using it in the existing chart required:- the existing seceret be named according to a specific pattern
{{ $.Release.Name }}-postgresql
; - provide a dummy
postgresql.auth.password
to avoid theminiflux
chart using the admin password
- the existing seceret be named according to a specific pattern
values.yaml
ingress:
main:
enabled: true
className: nginx
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
hosts:
- host: read.estradiol.cloud
paths:
- path: /
tls:
- hosts:
- read.estradiol.cloud
secretName: miniflux-tls
postgresql:
enabled: true
auth:
database: miniflux
username: miniflux
password: usused-chart-hack
existingSecret: miniflux-postgresql
persistence:
enabled: true
size: 10Gi