Richard Hagen

After starting the container and Uptime-kuma, you have to get a shell in the container, and execute `node extra/map-ingress.js` :)

Hi! Notice this error in the output: `Error: Request failed with status code 403`, you might have forgotten, or made a mistake in the RBAC configuration? the service account that...

Did you specify that `statefulset.apps/uptime` uses the `uptime-kuma-test` serviceAccount? Can you post `uptime-test.yaml` (or the yaml for `statefulset.apps/uptime`)?

Yup, here is my Deployment: ``` (node:1) UnhandledPromiseRejectionWarning: Error: select * from `tag` where name = 'Ingress' limit 1 - SQLITE_ERROR: no such table: tag ``` This means that the...

Hehe, definitly more documentation! I insert the monitor as UserID 1 by default, but if that user doesnt exist/have been created yet, you would get that error :) So make...

Unfortunatly not, because we can't tell UptimeKuma to refresh the list of monitors, only a restart, or using the regular API will do that

Solved it last time by deleting 90% of our clusters, but happened again today... What is the proper solution for this? I deleted all PostgresClusters that didnt come up automatically,...

It feels like PGO has some kind of race condition when there are a bunch of clusters and I remove failed restore jobs at the wrong time 🤔

Yes, I do have many clusters named eportaldb in different namespaces (dev, staging, prod) and We create a clone in staging on a new pull-request coming in, so is *very*...

So, after studying the topic some more, apparantly they want us to construct a access token (JWT), and sign it with my JWK (RSA key above). For HelseID Provider, they...