This repo contains the automation to repackage uptime-kuma into a non-root OCI container image as well as a simple Helm 3 Chart to deploy on OpenShift, but also on Kubernetes.
The Helm Chart will deploy a single Pod as part of a StatefulSet, you can configure persistence and optionally deploy a OpenShift Route or regular K8s Ingress alongside.
To use the ServiceMonitor you can enable it by adding serviceMonitor.enabled=true to your values.yaml
To use this you will have to startup uptime-kuma, go to Settings → API Keys → Create a key and copy the token. Than add a secret to your namespace that looks like the source file below. Make you you fill in the username and the password. The username should be the username you use to login. The password should be the token you just generated. If you do not use Authentication in Kuma you can skip this part.
---
apiVersion: v1
kind: Secret
metadata:
name: uptime-kuma-credentials
type: Opaque
data:
username: <username>
password: <token>
---The custom image within this repo is built with the intent to repackage uptime-kuma in an OpenShift compatible way (i.e. to support and work properly with arbitrary UIDs), therefor the image is also a non-root image.
It is used within this chat and its sources can be fund under the container folder within this repo or here:
link:./container/Containerfile[role=include]I published a prebuilt version of this to Quay.io and reference that within the Chart, feel free to use that or build it yourself 😉.
Alternatively, the image is also pushed to ghcr.io (GitHub Container registry) so there is a backup mirror when you run into issues with Quay.
|
Important
|
Please note that this is plainly an UNOFFICIAL way to install uptime-kuma. So please do not expect to get help and or support in the official uptime-kuma issues or other forms of help sections! |
This Helm Chart and the image where validated against Open Shift 4.x, yet they should work fine with regular Kubernetes.
I will try to keep this Chart and container image updated and operational, yet it may take me a moment to get to the latest uptime-kuma release (~1-2 days usually).