Compare commits

..

23 Commits

Author SHA1 Message Date
admin f189a742cd renovate: remove orphan } left by previous cleanup PR (#85)
The previous PR deleted the umami packageRule but left a stray closing
brace after it, which broke the embedded config.json. ArgoCD applied
the manifest as a string (it's a ConfigMap; k8s doesn't validate the
JSON inside data), so the live ConfigMap also has the invalid JSON --
next Renovate run would fail to parse the config.

Removing the orphan brace restores valid JSON. Verified `json.loads`
parses to 3 customManagers + 7 packageRules.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 15:11:52 +02:00
admin c973d491ce Merge pull request 'cleanup: drop felhom-system stale copies + fix plex datasource + drop obsolete umami config' (#85) from cleanup/felhom-stale-plex-renovate into main 2026-06-06 13:05:00 +00:00
admin ee93b504fa cleanup: drop stale felhom-system copies + fix plex datasource + remove obsolete umami config
Three coordinated changes, all surfaced by the question "will Renovate
track the manually-bumped packages going forward":

1) Delete `felhom-system/` directory (4 files).
   These were never the source of truth -- the `felhom` ArgoCD app
   pulls from `felhom.eu`, path `manifests`. The copies in this repo
   fell out of sync over time and were misleading. Renovate was about
   to start opening DEAD PRs against them (the customManager below
   targeted `felhom-system/umami.yaml`). Removing the directory is the
   cleanest fix; manual bumps for the real felhom-system manifests go
   into the felhom.eu repo.

2) Fix plex inline `# renovate:` comment in helm/plex/values.yaml.
   It referenced `datasource=custom.plex` but no such customDatasource
   exists in the config -- Renovate would silently skip plex. Switched
   to the standard docker datasource with regex versioning that parses
   `1.X.Y.Z-<hash>` (4 segments + git short-hash suffix, same pattern
   approach as servarr and termix).

3) Remove the now-obsolete umami customManager + packageRule.
   The customManager was for the `postgresql-vX.Y.Z` tag form we've
   abandoned -- the real felhom.eu deployment is on `3.1.0` (plain
   semver). The packageRule disabled the kubernetes manager for the
   umami image to silence its failure on `postgresql-vX.Y.Z`; not
   needed since the default versioning handles `3.X.Y` fine. (Moot
   anyway since Renovate doesn't watch felhom.eu -- but cleanup
   reduces config noise.)

After this PR, Renovate's effective tracking:
  - servarr (sonarr/radarr/prowlarr)      -> YES (customManager)
  - plex                                   -> YES (inline comment, docker)
  - termix                                 -> YES (customManager)
  - umami / filebrowser in felhom.eu      -> NO (different repo, manual)
  - all standard semver/named tags in homelab-manifests -> YES (defaults)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 15:04:59 +02:00
admin 6caf521c1f Merge pull request 'feat: bump servarr (sonarr/radarr/prowlarr) + plex image tags' (#84) from feat/servarr-plex-bumps into main 2026-06-06 12:16:25 +00:00
admin 0f2ff3fa52 servarr + plex: bump image tags
- sonarr     version-4.0.16.2944 -> version-4.0.17.2952  (patch within 4.0.x)
  - radarr×2   version-6.0.4.10291 -> version-6.1.1.10360  (minor within 6.x)
  - prowlarr   version-2.3.0.5236  -> version-2.3.5.5327   (patch within 2.3.x)
  - plex       1.43.0.10467-...    -> 1.43.2.10687-...     (patch within 1.43.x)

All four were stuck because of tag-format issues that I addressed in
PR #82 (servarr customManager) / PR #83. Renovate isn't auto-creating
the PRs yet (DH rate-limit), so doing them manually so version-checker
clears.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 14:16:24 +02:00
admin 6f49a21b3d Merge pull request 'fix: re-pin moving tags (filebrowser/umami/recipes) so Renovate can track them' (#83) from fix/moving-tag-repins into main 2026-06-06 11:35:13 +00:00
admin d92d2c31a6 re-pin moving tags so Renovate can track them
Renovate can't propose updates for moving tags (the tag string never
changes; the registry just points it at a different image). These three
were pinned to moving variants:

  felhom-system/webpage.yaml : filebrowser/filebrowser:v2-alpine
  felhom-system/umami.yaml   : ghcr.io/umami-software/umami:postgresql-latest
  tandoor-system/tandoor.yaml: vabene1111/recipes:2.6

Pin each to the current actual version per Viktor's call:
  - filebrowser -> v2.63.13 (matches the other 4 filebrowser pinnings
    in the repo; dropped the `-alpine` variant so Renovate can group
    them via the existing default datasource path)
  - umami       -> postgresql-v1.38.0 (current upstream postgresql
    variant latest; tracked via new customManager below)
  - recipes     -> 2.6.9 (current actual semver of the 2.6 series)

For umami, the `postgresql-vX.Y.Z` tag pattern is rejected by Renovate's
default docker versioning pre-check (same failure class as termix +
linuxserver servarr). Added a customManager regex + packageRule disable
pair so Renovate can track future `postgresql-vX.Y.Z` updates via regex
versioning. filebrowser and recipes use standard semver `X.Y.Z` after
the re-pin and need no special handling.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 13:35:12 +02:00
admin 6ca0a7b051 Merge pull request 'fix: version tracking tuning — annotations + linuxserver customManager' (#82) from fix/version-tracking-tuning into main 2026-06-06 11:25:51 +00:00
admin 1d08156d81 version tracking: tune annotations + add customManagers for linuxserver servarr
Several images were showing as outdated in version-checker / unhandled by
Renovate. Each had a distinct cause; this PR fixes the auto-tractable ones.

1) admin-system/renovate.yaml: bump `app.kubernetes.io/version` labels
   `43.197.0 -> 43.209.3` (3 occurrences) to match the live image.
   Renovate's own self-update PR bumped the image tag but left the
   labels stale; the version-checker widget appears to read the label.
   Long-term, this label will drift again on each self-update -- worth
   a customManager later if it becomes a recurring annoyance.

2) admin-system/renovate.yaml: add a customManager + packageRule pair
   for linuxserver servarr apps. Tag pattern is `version-X.Y.Z.B`
   (4 segments + `version-` prefix) which the kubernetes manager's
   default docker versioning rejects at the pre-check, same failure
   class as termix. Regex versioning parses the prefixed 4-segment
   form; the same customManager handles prowlarr/radarr/sonarr (depName
   captured from the regex). kubernetes-manager extraction for these
   three depnames is disabled via packageRule so the dashboard isn't
   cluttered with the failing fallback.

3) nextcloud-system/nextcloud.yaml: add
   `match-regex.version-checker.io/nextcloud: '^\d+\.\d+\.\d+-apache$'`
   so version-checker doesn't treat the bare `33.0.5` server tag as a
   newer version of our `33.0.5-apache` image. The widget was showing
   `33.0.5-apache -> 33.0.5` -- false positive; image is already current.

4) helm/plex/values.yaml: tighten the version-checker regex from
   `^\d+\.\d+\.\d+\.\d+-.*$` to `^\d+\.\d+\.\d+\.\d+-[a-f0-9]+$` so
   per-arch tags (`-armhf`, `-arm64`, ...) are excluded. The widget
   was showing an `-armhf` tag as "newer" than our x86_64 install.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 13:25:49 +02:00
admin a8c657d554 Merge pull request 'pihole: bump image to 2026.05.0 (dnsmasq CVE security release)' (#81) from feat/pihole-2026.05.0 into main 2026-06-06 10:56:00 +00:00
admin 9e020af94d pihole: bump image to 2026.05.0 (dnsmasq CVE security release)
Pi-hole 2026.05.0 bundles FTL v6.6.2 which imports six upstream dnsmasq
security fixes, covering all publicly disclosed CVEs against the
dnsmasq 2.92/2.93 line. Per the upstream release notes the fixes are
"minimal, self-contained changes to the embedded dnsmasq sources. No
FTL-side configuration or API changes; users should see no observable
behavior change beyond the closed vulnerabilities."

Override the chart's default image.tag in helm/pihole/values.yaml (no
chart version bump). The pihole ArgoCD app is intentionally MANUAL
sync per Viktor's call -- after merge, sync the pihole app from the
ArgoCD UI to roll the pod over.

https://github.com/pi-hole/docker-pi-hole/releases/tag/2026.05.0

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 12:55:58 +02:00
admin ec9ae43bee Merge pull request 'termix: manual bump 1.11.2 -> 2.3.2 (Renovate blocked by DH rate-limit)' (#80) from feat/termix-v2.3.2 into main 2026-06-06 09:16:02 +00:00
admin e822b76982 termix: manual bump 1.11.2 -> 2.3.2 (Renovate blocked by DH rate-limit)
Renovate's `Pending Approval` checkbox for the termix v2 major was ticked
on Dashboard #6, but the manual Renovate runs that should have processed
it both aborted on Docker Hub's authenticated rate-limit:

  HTTP 429: You have reached your pull rate limit as 'kisfenyo'

The free DH plan caps authenticated pulls at 100/6h; with ~270 deps in
this repo and the multiple runs we've done today, we've exhausted it.
Renovate's behavior on a host 429 is to abort the entire repository run
(`result: external-host-error`), so no further work — including ticked
dashboard approvals — gets done until the quota window resets.

Rather than wait ~3-4 hours, this PR does the bump by hand. Upstream
ghcr.io/lukegus/termix:release-2.3.2 is verified present (Termix-SSH
GitHub Release of 2026-06-04). Termix is stateless (host/cred config
stored in PocketBase but compatible across release-1 and release-2),
so the rollout should be a straightforward image swap.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 11:16:00 +02:00
admin 876b044d0a Merge pull request 'fix: roll back immich-postgres v17 -> v16 (PG major incompat) + gate postgres-family' (#79) from fix/immich-postgres-rollback into main 2026-06-06 09:00:33 +00:00
admin e459b0d262 immich/renovate: roll back immich-postgres v17 -> v16 (PG major datadir incompat) + gate postgres-family images
Renovate PR #76 (merged 2026-06-06 10:48) bumped ghcr.io/immich-app/postgres
from `16-vectorchord0.3.0` to `17-vectorchord0.3.0`. PostgreSQL major
upgrades require pg_upgrade or pg_dump/restore — the new server binary
refuses to open a data directory initialized by the previous major:

  FATAL: database files are incompatible with server
  DETAIL: The data directory was initialized by PostgreSQL version 16,
          which is not compatible with this version 17.6

Both immich-postgres and immich-server (depends on Postgres) went into
CrashLoopBackOff. PVC still holds the v16 datadir.

This PR:
  1. Reverts ghcr.io/immich-app/postgres back to `16-vectorchord0.3.0`
     so immich recovers immediately.
  2. Adds a packageRule with `dependencyDashboardApproval: true` covering
     `postgres`, `postgis/postgis`, and `ghcr.io/immich-app/postgres`.
     Any update to these images is now held on the Dashboard's "Pending
     Approval" section -- Renovate won't even open a PR until the user
     explicitly ticks the box. Forces the migration plan to be made
     BEFORE the change reaches main.

This is the same recovery pattern we just used for meilisearch (PR #77)
-- a class of stateful images where the on-disk format isn't
forward-compatible across version bumps.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-06 11:00:32 +02:00
admin 99bbc31325 Merge pull request 'Update docker.io/library/nextcloud Docker tag to v33.0.5' (#78) from renovate/docker.io-library-nextcloud-33.x into main 2026-06-06 09:00:24 +00:00
Renovate Bot fee5fafeb0 Update docker.io/library/nextcloud Docker tag to v33.0.5
renovate/stability-days Updates have not met minimum release age requirement
2026-06-06 09:00:21 +00:00
admin 25c1baf1c3 Merge pull request 'Update grafana/grafana Docker tag to v13' (#58) from renovate/grafana-grafana-13.x into main
Reviewed-on: #58
2026-06-06 08:56:24 +00:00
admin 184c469c51 Merge pull request 'Update redis Docker tag to v8' (#64) from renovate/redis-8.x into main
Reviewed-on: #64
2026-06-06 08:56:16 +00:00
admin 6291423776 Merge pull request 'Update ghcr.io/cloudnative-pg/cloudnative-pg Docker tag to v1.29.1' (#70) from renovate/ghcr.io-cloudnative-pg-cloudnative-pg-1.x into main
Reviewed-on: #70
2026-06-06 08:56:08 +00:00
Renovate Bot e0550cbe54 Update ghcr.io/cloudnative-pg/cloudnative-pg Docker tag to v1.29.1
renovate/stability-days Updates have not met minimum release age requirement
2026-06-06 08:33:11 +00:00
Renovate Bot 56d39399d6 Update redis Docker tag to v8
renovate/stability-days Updates have met minimum release age requirement
2026-06-06 07:53:16 +00:00
Renovate Bot a2e68c1745 Update grafana/grafana Docker tag to v13
renovate/stability-days Updates have met minimum release age requirement
2026-06-06 07:52:33 +00:00
20 changed files with 67 additions and 934 deletions
+34 -4
View File
@@ -62,6 +62,17 @@ data:
"packageNameTemplate": "Termix-SSH/Termix",
"versioningTemplate": "regex:^release-(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)$",
"extractVersionTemplate": "^(?<version>release-\\d+\\.\\d+\\.\\d+)"
},
{
"description": "linuxserver servarr apps (prowlarr, radarr, sonarr) use tag pattern `version-X.Y.Z.B` (4 segments + `version-` prefix). The kubernetes manager's default docker versioning rejects them at the pre-check (same failure class as termix), so no PRs ever open. Use regex versioning to parse the prefixed 4-segment form; depName is captured from the regex so the same customManager handles all three apps.",
"customType": "regex",
"managerFilePatterns": ["/servarr-system/.+\\.ya?ml$/"],
"matchStrings": [
"image:\\s+linuxserver/(?<depName>prowlarr|radarr|sonarr):(?<currentValue>version-\\d+\\.\\d+\\.\\d+\\.\\d+)"
],
"datasourceTemplate": "docker",
"packageNameTemplate": "linuxserver/{{depName}}",
"versioningTemplate": "regex:^version-(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)\\.(?<build>\\d+)$"
}
],
"packageRules": [
@@ -114,11 +125,30 @@ data:
"matchPackageNames": ["getmeili/meilisearch"],
"dependencyDashboardApproval": true
},
{
"description": "Postgres-family images: a major bump (e.g. 16 -> 17) requires pg_upgrade or dump/restore — the new server binary refuses to open the old data directory (`database files are incompatible with server`). PR #76 (immich-app/postgres 16 -> 17) on 2026-06-06 crashlooped immich-postgres and immich-server. Renovate's docker versioning treats these custom tag formats inconsistently, so don't trust the major/minor classification: hold ALL updates for these images behind explicit dashboard approval. Includes vanilla postgres, postgis/postgis (where the tag prefix IS the pg major), and ghcr.io/immich-app/postgres (custom `N-vectorchordX.Y.Z` form).",
"matchPackageNames": [
"postgres",
"postgis/postgis",
"ghcr.io/immich-app/postgres"
],
"dependencyDashboardApproval": true
},
{
"description": "termix: kubernetes manager would extract the image with versioning=docker and silently skip it (release-1.11.0 fails the docker pre-check). Disable that extraction; customManagers above does the real work via github-releases.",
"matchManagers": ["kubernetes"],
"matchPackageNames": ["ghcr.io/lukegus/termix"],
"enabled": false
},
{
"description": "linuxserver servarr apps: same disable pattern as termix. The customManager above handles extraction with the right versioning; turn off the default kubernetes-manager extraction so it doesn't silently skip + clutter the dashboard.",
"matchManagers": ["kubernetes"],
"matchPackageNames": [
"linuxserver/prowlarr",
"linuxserver/radarr",
"linuxserver/sonarr"
],
"enabled": false
}
],
"labels": ["renovate"]
@@ -132,7 +162,7 @@ metadata:
labels:
app.kubernetes.io/instance: renovate
app.kubernetes.io/name: renovate
app.kubernetes.io/version: "43.197.0"
app.kubernetes.io/version: "43.209.3"
spec:
# Sat 02:00 Europe/Budapest — leaves the full weekend for troubleshooting
# if a Renovate-merged update breaks something.
@@ -147,14 +177,14 @@ spec:
labels:
app.kubernetes.io/instance: renovate
app.kubernetes.io/name: renovate
app.kubernetes.io/version: "43.197.0"
app.kubernetes.io/version: "43.209.3"
spec:
template:
metadata:
labels:
app.kubernetes.io/instance: renovate
app.kubernetes.io/name: renovate
app.kubernetes.io/version: "43.197.0"
app.kubernetes.io/version: "43.209.3"
annotations:
# Renovate uses plain X.Y.Z semver tags (no -slim suffix anymore)
match-regex.version-checker.io/renovate: '^\d+\.\d+\.\d+$'
@@ -163,7 +193,7 @@ spec:
restartPolicy: OnFailure
containers:
- name: renovate
image: renovate/renovate:43.214.1
image: renovate/renovate:43.209.3
imagePullPolicy: IfNotPresent
envFrom:
- secretRef:
+1 -1
View File
@@ -56,7 +56,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7.4-alpine
image: redis:8.8-alpine
ports:
- containerPort: 6379
name: redis
+1 -1
View File
@@ -77,7 +77,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7-alpine
image: redis:8-alpine
imagePullPolicy: IfNotPresent
args:
- redis-server
+1 -1
View File
@@ -57,7 +57,7 @@ replicaCount: 1
# Image configuration (optional - use defaults)
image:
repository: ghcr.io/cloudnative-pg/cloudnative-pg
tag: 1.28.1
tag: 1.29.1
# Service configuration
service:
-142
View File
@@ -1,142 +0,0 @@
# Contact Mailer - Lightweight email sender for felhom.eu contact form
# Uses Resend.com API for transactional email delivery.
#
# PREREQUISITES:
# 1. Build and push the container image:
# docker build -t contact-mailer:latest .
# # Option A: Push to Gitea registry (if configured):
# # docker tag contact-mailer:latest gitea.felhom.eu/felhom/contact-mailer:latest
# # docker push gitea.felhom.eu/felhom/contact-mailer:latest
# # Option B: Import directly into k3s (single node):
# # docker save contact-mailer:latest | sudo k3s ctr images import -
#
# 2. Create the Secret with your Resend API key:
# kubectl create secret generic contact-mailer-config \
# --namespace=felhom-system \
# --from-literal=RESEND_API_KEY='re_xxxxxxxxxxxx'
#
# 3. Apply this manifest:
# kubectl apply -f contact-mailer.yaml
#
# 4. Test:
# # Health check:
# curl https://felhom.eu/api/healthz
# # Send test email (only works if DEBUG=true):
# curl -X POST https://felhom.eu/api/debug/test
#
# 5. Update contact form endpoint in kapcsolat.html:
# CONFIG.formEndpoint = '/api/contact';
#
# DEBUGGING:
# kubectl logs -n felhom-system deploy/contact-mailer -f
# kubectl exec -it -n felhom-system deploy/contact-mailer -- wget -qO- http://localhost:8080/healthz
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: contact-mailer
namespace: felhom-system
labels:
app: contact-mailer
spec:
replicas: 1
selector:
matchLabels:
app: contact-mailer
template:
metadata:
labels:
app: contact-mailer
spec:
containers:
- name: contact-mailer
image: contact-mailer:latest
# Use 'Never' for locally imported images, 'Always' for registry
imagePullPolicy: Never
ports:
- containerPort: 8080
env:
- name: RESEND_API_KEY
valueFrom:
secretKeyRef:
name: contact-mailer-config
key: RESEND_API_KEY
- name: FROM_EMAIL
value: "Felhom.eu <noreply@felhom.eu>"
- name: TO_EMAIL
value: "info@felhom.eu"
- name: ALLOWED_ORIGIN
value: "https://felhom.eu"
- name: TZ
value: "Europe/Budapest"
# Set to "true" to enable /debug/test endpoint
- name: DEBUG
value: "false"
resources:
requests:
memory: "16Mi"
cpu: "5m"
limits:
memory: "64Mi"
cpu: "100m"
livenessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 5
periodSeconds: 30
readinessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 3
periodSeconds: 10
securityContext:
runAsNonRoot: true
runAsUser: 1000
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
---
apiVersion: v1
kind: Service
metadata:
name: contact-mailer
namespace: felhom-system
spec:
selector:
app: contact-mailer
ports:
- port: 80
targetPort: 8080
---
# Ingress: routes felhom.eu/api/* to the contact mailer
# This is a SEPARATE ingress from the website - nginx-ingress merges them
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: contact-mailer
namespace: felhom-system
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
# Allow larger uploads for attachments
nginx.ingress.kubernetes.io/proxy-body-size: "25m"
# Timeout for large file uploads
nginx.ingress.kubernetes.io/proxy-read-timeout: "60"
nginx.ingress.kubernetes.io/proxy-send-timeout: "60"
spec:
ingressClassName: nginx-internal
tls:
- hosts:
- felhom.eu
secretName: felhom-webpage-tls
rules:
- host: felhom.eu
http:
paths:
- path: /api
pathType: Prefix
backend:
service:
name: contact-mailer
port:
number: 80
-194
View File
@@ -1,194 +0,0 @@
# Healthchecks - Self-hosted cron/backup monitoring with dead man's switch
# Dashboard: https://status.felhom.eu
# Ping endpoint: https://status.felhom.eu/ping/<uuid>
#
# Customer servers ping this after successful backup.
# If a ping is missed, Healthchecks sends email alerts.
#
# After deploying, create superuser:
# kubectl exec -it -n felhom-system deploy/healthchecks -- python manage.py createsuperuser
#
# SMTP: Configure the Secret below with your email provider credentials.
# Recommended free options:
# - Resend.com (3000 emails/month free, easy setup)
# - Brevo/Sendinblue (300 emails/day free)
# - SMTP2GO (1000 emails/month free)
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: healthchecks-data
namespace: felhom-system
spec:
accessModes:
- ReadWriteOnce
storageClassName: longhorn
resources:
requests:
storage: 1Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: healthchecks
namespace: felhom-system
labels:
app: healthchecks
spec:
replicas: 1
selector:
matchLabels:
app: healthchecks
template:
metadata:
labels:
app: healthchecks
spec:
securityContext:
fsGroup: 999
containers:
- name: healthchecks
image: healthchecks/healthchecks:v4.2
ports:
- containerPort: 8000
env:
# --- Site settings ---
- name: SITE_ROOT
value: "https://status.felhom.eu"
- name: SITE_NAME
value: "Felhom Monitoring"
- name: ALLOWED_HOSTS
value: "status.felhom.eu"
- name: PING_ENDPOINT
value: "https://status.felhom.eu/ping/"
- name: DEBUG
value: "False"
- name: REGISTRATION_OPEN
value: "False"
- name: DB
value: "sqlite"
- name: DB_NAME
value: "/data/hc.sqlite"
- name: TZ
value: "Europe/Budapest"
# --- Secrets (from Secret) ---
- name: SECRET_KEY
valueFrom:
secretKeyRef:
name: healthchecks-config
key: SECRET_KEY
- name: SUPERUSER_EMAIL
valueFrom:
secretKeyRef:
name: healthchecks-config
key: SUPERUSER_EMAIL
- name: SUPERUSER_PASSWORD
valueFrom:
secretKeyRef:
name: healthchecks-config
key: SUPERUSER_PASSWORD
- name: EMAIL_HOST
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_HOST
- name: EMAIL_PORT
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_PORT
- name: EMAIL_HOST_USER
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_HOST_USER
- name: EMAIL_HOST_PASSWORD
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_HOST_PASSWORD
- name: EMAIL_USE_TLS
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_USE_TLS
- name: EMAIL_USE_VERIFICATION
valueFrom:
secretKeyRef:
name: healthchecks-config
key: EMAIL_USE_VERIFICATION
- name: DEFAULT_FROM_EMAIL
valueFrom:
secretKeyRef:
name: healthchecks-config
key: DEFAULT_FROM_EMAIL
volumeMounts:
- name: data
mountPath: /data
resources:
requests:
memory: "128Mi"
cpu: "50m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /api/v3/status/
port: 8000
httpHeaders:
- name: Host
value: status.felhom.eu
initialDelaySeconds: 30
periodSeconds: 60
readinessProbe:
httpGet:
path: /api/v3/status/
port: 8000
httpHeaders:
- name: Host
value: status.felhom.eu
initialDelaySeconds: 10
periodSeconds: 10
volumes:
- name: data
persistentVolumeClaim:
claimName: healthchecks-data
---
apiVersion: v1
kind: Service
metadata:
name: healthchecks
namespace: felhom-system
spec:
selector:
app: healthchecks
ports:
- port: 80
targetPort: 8000
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: healthchecks
namespace: felhom-system
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
ingressClassName: nginx-internal
tls:
- hosts:
- status.felhom.eu
secretName: healthchecks-tls
rules:
- host: status.felhom.eu
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: healthchecks
port:
number: 80
-288
View File
@@ -1,288 +0,0 @@
# Umami v3 - Privacy-focused web analytics for felhom.eu
# Dashboard: https://stats.felhom.eu
# Tracking: Add <script> tag to website HTML pages (see bottom of file)
#
# Umami v3 requires PostgreSQL (no SQLite/MySQL support).
# This manifest deploys a dedicated small PostgreSQL instance alongside Umami
# to keep it self-contained within the felhom-system namespace.
#
# PREREQUISITES:
# 1. Create the Secret with credentials:
# APP_SECRET: Random string for session encryption (generate with: openssl rand -hex 32)
# POSTGRES_PASSWORD: Database password (generate with: openssl rand -hex 16)
#
# kubectl create secret generic umami-config \
# --namespace=felhom-system \
# --from-literal=APP_SECRET="$(openssl rand -hex 32)" \
# --from-literal=POSTGRES_PASSWORD="$(openssl rand -hex 16)"
#
# 2. Apply this manifest:
# kubectl apply -f umami.yaml
#
# 3. Wait for pods to be ready (~30-60 seconds for first start, DB init):
# kubectl get pods -n felhom-system -l app=umami -w
# kubectl get pods -n felhom-system -l app=umami-db -w
#
# 4. Login at https://stats.felhom.eu
# Default credentials: admin / umami
# ⚠️ CHANGE THE PASSWORD IMMEDIATELY after first login!
#
# 5. Add your website in Umami:
# Settings → Websites → Add website → Name: "felhom.eu", Domain: "felhom.eu"
# Copy the tracking code and add it to your HTML pages (see bottom of file).
#
# DEBUGGING:
# kubectl logs -n felhom-system deploy/umami -f
# kubectl logs -n felhom-system deploy/umami-db -f
# kubectl exec -it -n felhom-system deploy/umami -- wget -qO- http://localhost:3000/api/heartbeat
# kubectl exec -it -n felhom-system deploy/umami-db -- pg_isready -U umami
#
# BACKUP:
# # Dump the database:
# kubectl exec -n felhom-system deploy/umami-db -- pg_dump -U umami umami > umami-backup-$(date +%Y%m%d).sql
# # Restore:
# cat umami-backup-YYYYMMDD.sql | kubectl exec -i -n felhom-system deploy/umami-db -- psql -U umami umami
# =============================================================================
# PERSISTENT STORAGE
# =============================================================================
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: umami-db-data
namespace: felhom-system
spec:
accessModes:
- ReadWriteOnce
storageClassName: longhorn
resources:
requests:
storage: 2Gi
# =============================================================================
# POSTGRESQL - Dedicated database for Umami
# =============================================================================
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: umami-db
namespace: felhom-system
labels:
app: umami-db
spec:
replicas: 1
strategy:
type: Recreate
selector:
matchLabels:
app: umami-db
template:
metadata:
labels:
app: umami-db
spec:
containers:
- name: postgres
image: postgres:16-alpine
ports:
- containerPort: 5432
env:
- name: POSTGRES_DB
value: "umami"
- name: POSTGRES_USER
value: "umami"
- name: POSTGRES_PASSWORD
valueFrom:
secretKeyRef:
name: umami-config
key: POSTGRES_PASSWORD
- name: PGDATA
value: "/var/lib/postgresql/data/pgdata"
volumeMounts:
- name: data
mountPath: /var/lib/postgresql/data
resources:
requests:
memory: "64Mi"
cpu: "25m"
limits:
memory: "256Mi"
cpu: "500m"
livenessProbe:
exec:
command:
- pg_isready
- -U
- umami
initialDelaySeconds: 15
periodSeconds: 30
readinessProbe:
exec:
command:
- pg_isready
- -U
- umami
initialDelaySeconds: 5
periodSeconds: 10
volumes:
- name: data
persistentVolumeClaim:
claimName: umami-db-data
---
apiVersion: v1
kind: Service
metadata:
name: umami-db
namespace: felhom-system
spec:
selector:
app: umami-db
ports:
- port: 5432
targetPort: 5432
# =============================================================================
# UMAMI - Web Analytics Application
# =============================================================================
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: umami
namespace: felhom-system
labels:
app: umami
spec:
replicas: 1
selector:
matchLabels:
app: umami
template:
metadata:
labels:
app: umami
spec:
# Wait for DB to be available before starting Umami
initContainers:
- name: wait-for-db
image: postgres:16-alpine
command:
- sh
- -c
- |
echo "Waiting for PostgreSQL to be ready..."
until pg_isready -h umami-db -p 5432 -U umami; do
echo " ...still waiting"
sleep 2
done
echo "PostgreSQL is ready!"
resources:
requests:
memory: "16Mi"
cpu: "5m"
limits:
memory: "32Mi"
cpu: "50m"
containers:
- name: umami
image: ghcr.io/umami-software/umami:postgresql-latest
ports:
- containerPort: 3000
env:
- name: POSTGRES_PASSWORD
valueFrom:
secretKeyRef:
name: umami-config
key: POSTGRES_PASSWORD
- name: DATABASE_URL
value: "postgresql://umami:$(POSTGRES_PASSWORD)@umami-db:5432/umami"
- name: APP_SECRET
valueFrom:
secretKeyRef:
name: umami-config
key: APP_SECRET
# Disable Umami's own telemetry
- name: DISABLE_TELEMETRY
value: "1"
- name: TZ
value: "Europe/Budapest"
resources:
requests:
memory: "128Mi"
cpu: "50m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /api/heartbeat
port: 3000
initialDelaySeconds: 30
periodSeconds: 30
readinessProbe:
httpGet:
path: /api/heartbeat
port: 3000
initialDelaySeconds: 15
periodSeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: umami
namespace: felhom-system
spec:
selector:
app: umami
ports:
- port: 80
targetPort: 3000
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: umami
namespace: felhom-system
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
ingressClassName: nginx-internal
tls:
- hosts:
- stats.felhom.eu
secretName: umami-tls
rules:
- host: stats.felhom.eu
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: umami
port:
number: 80
# =============================================================================
# TRACKING SCRIPT - Add to your HTML pages
# =============================================================================
#
# After deploying and creating your website in Umami, add this to every page's
# <head> section (replace WEBSITE_ID with the ID from Umami dashboard):
#
# <script defer src="https://stats.felhom.eu/script.js" data-website-id="YOUR-WEBSITE-ID"></script>
#
# The script is <2KB, async/deferred, cookie-free, and GDPR compliant.
# No cookie consent banner needed!
#
# TIP: Since your HTML files are managed via FileBrowser, you can add the
# script tag to all pages at once. Add it right before </head> in:
# - index.html
# - alkalmazasok.html
# - technologiak.html
# - gyik.html
# - kapcsolat.html
# - biztonsagimentes.html (if exists)
# - Any other pages
-286
View File
@@ -1,286 +0,0 @@
# FileBrowser + Webpage deployment for felhom.eu
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: felhom-website-content
namespace: felhom-system
spec:
accessModes:
- ReadWriteMany
storageClassName: longhorn
resources:
requests:
storage: 1Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: filebrowser-db
namespace: felhom-system
spec:
accessModes:
- ReadWriteOnce
storageClassName: longhorn
resources:
requests:
storage: 100Mi
---
apiVersion: v1
kind: ConfigMap
metadata:
name: filebrowser-config
namespace: felhom-system
data:
.filebrowser.json: |
{
"port": 8080,
"baseURL": "",
"address": "0.0.0.0",
"log": "stdout",
"database": "/database/filebrowser.db",
"root": "/srv"
}
---
# ===================
# NGINX CONFIG FOR CLEAN URLs
# ===================
apiVersion: v1
kind: ConfigMap
metadata:
name: nginx-config
namespace: felhom-system
data:
default.conf: |
server {
listen 80;
server_name _;
root /usr/share/nginx/html;
index index.html;
# Enable clean URLs - serve .html files without extension
location / {
try_files $uri $uri.html $uri/ =404;
}
# Cache static assets
location ~* \.(css|js|png|jpg|jpeg|gif|ico|svg|woff|woff2)$ {
expires 7d;
add_header Cache-Control "public, immutable";
}
# Security headers
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-Content-Type-Options "nosniff" always;
# Error pages
error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;
}
---
# ===================
# FILEBROWSER
# ===================
apiVersion: apps/v1
kind: Deployment
metadata:
name: filebrowser
namespace: felhom-system
labels:
app: filebrowser
spec:
replicas: 1
selector:
matchLabels:
app: filebrowser
template:
metadata:
labels:
app: filebrowser
spec:
containers:
- name: filebrowser
image: filebrowser/filebrowser:v2-alpine
ports:
- containerPort: 8080
volumeMounts:
- name: website-content
mountPath: /srv
- name: database
mountPath: /database
- name: config
mountPath: /.filebrowser.json
subPath: .filebrowser.json
resources:
requests:
memory: "64Mi"
cpu: "50m"
limits:
memory: "256Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 10
periodSeconds: 30
readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 5
periodSeconds: 10
volumes:
- name: website-content
persistentVolumeClaim:
claimName: felhom-website-content
- name: database
persistentVolumeClaim:
claimName: filebrowser-db
- name: config
configMap:
name: filebrowser-config
---
apiVersion: v1
kind: Service
metadata:
name: filebrowser
namespace: felhom-system
spec:
selector:
app: filebrowser
ports:
- port: 80
targetPort: 8080
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: filebrowser
namespace: felhom-system
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/proxy-body-size: "100m"
spec:
ingressClassName: nginx-internal
tls:
- hosts:
- files.felhom.eu
secretName: filebrowser-tls
rules:
- host: files.felhom.eu
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: filebrowser
port:
number: 80
---
# ===================
# WEBPAGE (nginx)
# ===================
apiVersion: apps/v1
kind: Deployment
metadata:
name: felhom-webpage
namespace: felhom-system
labels:
app: felhom-webpage
spec:
replicas: 1
selector:
matchLabels:
app: felhom-webpage
template:
metadata:
labels:
app: felhom-webpage
spec:
containers:
- name: nginx
image: nginx:alpine
ports:
- containerPort: 80
volumeMounts:
- name: website-content
mountPath: /usr/share/nginx/html
- name: nginx-config
mountPath: /etc/nginx/conf.d/default.conf
subPath: default.conf
resources:
requests:
memory: "32Mi"
cpu: "10m"
limits:
memory: "128Mi"
cpu: "200m"
livenessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 5
periodSeconds: 30
readinessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 3
periodSeconds: 10
volumes:
- name: website-content
persistentVolumeClaim:
claimName: felhom-website-content
- name: nginx-config
configMap:
name: nginx-config
---
apiVersion: v1
kind: Service
metadata:
name: felhom-webpage
namespace: felhom-system
spec:
selector:
app: felhom-webpage
ports:
- port: 80
targetPort: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: felhom-webpage
namespace: felhom-system
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
ingressClassName: nginx-internal
tls:
- hosts:
- felhom.eu
- www.felhom.eu
secretName: felhom-webpage-tls
rules:
- host: felhom.eu
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: felhom-webpage
port:
number: 80
- host: www.felhom.eu
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: felhom-webpage
port:
number: 80
+7
View File
@@ -1,4 +1,11 @@
---
# Image tag override: bumps pihole/pihole to 2026.05.0 without changing
# the chart version. The 2026.05.0 release bundles FTL v6.6.2 which
# imports 6 upstream dnsmasq CVE fixes (covering the dnsmasq 2.92/2.93
# disclosures). No FTL-side config or API changes per the release notes.
# https://github.com/pi-hole/docker-pi-hole/releases/tag/2026.05.0
image:
tag: "2026.05.0"
DNS1: "1.1.1.1" # Cloudflare
DNS2: "8.8.8.8" # Google
DNS3: "9.9.9.9" #Quad9
+6 -3
View File
@@ -3,8 +3,8 @@ image:
# -- The public dockerhub registry
registry: index.docker.io
repository: plexinc/pms-docker
# renovate: datasource=custom.plex depName=plex versioning=loose
tag: "1.43.0.10467-2b1ba6e69"
# renovate: datasource=docker depName=plexinc/pms-docker versioning=regex:^(?<major>\d+)\.(?<minor>\d+)\.(?<patch>\d+)\.(?<build>\d+)-[a-f0-9]+$
tag: "1.43.2.10687-563d026ea"
sha: ""
pullPolicy: IfNotPresent
@@ -235,7 +235,10 @@ statefulSet:
annotations: {}
# -- Optional extra annotations to add to the pods in the statefulset
podAnnotations:
match-regex.version-checker.io/plex-plex-media-server-pms: ^\d+\.\d+\.\d+\.\d+-.*$
# Match only `<X.Y.Z.B>-<short-hash>` (the amd64/native tag form) and exclude
# per-arch tags (e.g. `-armhf`, `-arm64`) so version-checker doesn't show an
# ARM tag as "newer" than our x86_64 install.
match-regex.version-checker.io/plex-plex-media-server-pms: '^\d+\.\d+\.\d+\.\d+-[a-f0-9]+$'
service:
type: LoadBalancer
+1 -1
View File
@@ -45,7 +45,7 @@ spec:
fsGroup: 999
containers:
- name: postgres
image: ghcr.io/immich-app/postgres:17-vectorchord0.3.0
image: ghcr.io/immich-app/postgres:16-vectorchord0.3.0
env:
- name: POSTGRES_USER
valueFrom:
+1 -1
View File
@@ -185,7 +185,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7-alpine
image: redis:8-alpine
imagePullPolicy: IfNotPresent
args:
- redis-server
+1 -1
View File
@@ -529,7 +529,7 @@ spec:
runAsGroup: 472
containers:
- name: grafana
image: grafana/grafana:12.4.4
image: grafana/grafana:13.0.2
ports:
- containerPort: 3000
name: http
+4 -1
View File
@@ -392,10 +392,13 @@ spec:
nextcloud-config-hash: 06b49913be13b1f9a81745166dd75ada59e7ddd39e8f6a2c5538affe2a6d1093
php-config-hash: 5a497358af870e06b42325eee83d7c0e5466b7f6819cb49b598559d96def7428
hooks-hash: 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a
# Only match the `X.Y.Z-apache` variant tags so version-checker doesn't
# treat the bare `X.Y.Z` server tag as a "newer" version of our apache image.
match-regex.version-checker.io/nextcloud: '^\d+\.\d+\.\d+-apache$'
spec:
containers:
- name: nextcloud
image: docker.io/library/nextcloud:33.0.4-apache
image: docker.io/library/nextcloud:33.0.5-apache
imagePullPolicy: IfNotPresent
env:
- name: SMTP_HOST
+1 -1
View File
@@ -198,7 +198,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7-alpine
image: redis:8-alpine
imagePullPolicy: IfNotPresent
command:
- redis-server
+1 -1
View File
@@ -71,7 +71,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7-alpine
image: redis:8-alpine
imagePullPolicy: IfNotPresent
ports:
- name: redis
+1 -1
View File
@@ -121,7 +121,7 @@ spec:
spec:
containers:
- name: redis
image: redis:7.4.9
image: redis:8.8.0
ports:
- containerPort: 6379
name: redis
+4 -4
View File
@@ -30,7 +30,7 @@ spec:
spec:
containers:
- name: prowlarr
image: linuxserver/prowlarr:version-2.3.0.5236
image: linuxserver/prowlarr:version-2.3.5.5327
imagePullPolicy: IfNotPresent
env:
- name: PUID
@@ -91,7 +91,7 @@ spec:
spec:
containers:
- name: radarr
image: linuxserver/radarr:version-6.0.4.10291
image: linuxserver/radarr:version-6.1.1.10360
imagePullPolicy: IfNotPresent
env:
- name: PUID
@@ -164,7 +164,7 @@ spec:
spec:
containers:
- name: sonarr
image: linuxserver/sonarr:version-4.0.16.2944
image: linuxserver/sonarr:version-4.0.17.2952
imagePullPolicy: IfNotPresent
env:
- name: PUID
@@ -705,7 +705,7 @@ spec:
spec:
containers:
- name: radarr
image: linuxserver/radarr:version-6.0.4.10291
image: linuxserver/radarr:version-6.1.1.10360
imagePullPolicy: IfNotPresent
env:
- name: PUID
+2 -2
View File
@@ -30,7 +30,7 @@ spec:
spec:
initContainers:
- name: create-superuser
image: vabene1111/recipes:2.6
image: vabene1111/recipes:2.6.9
workingDir: /opt/recipes
command:
- /bin/sh
@@ -106,7 +106,7 @@ spec:
key: email
containers:
- name: tandoor
image: vabene1111/recipes:2.6
image: vabene1111/recipes:2.6.9
imagePullPolicy: IfNotPresent
env:
- name: TZ
+1 -1
View File
@@ -45,7 +45,7 @@ spec:
# Renovate handles it via a customManagers regex defined in
# admin-system/renovate.yaml (the kubernetes manager doesn't
# process inline `# renovate:` comments).
image: ghcr.io/lukegus/termix:release-1.11.2
image: ghcr.io/lukegus/termix:release-2.3.2
imagePullPolicy: IfNotPresent
ports:
- name: http