starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Automation while deploying with kubernetes #532

New issue

Open

opened 2026-02-28 01:49:42 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-28 01:49:42 -05:00

Owner

Originally created by @DoNnMyTh on GitHub (Nov 5, 2021).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I would like to have a way with which i can create a pipeline or some other way to add monitoring probes.

✔️ Solution

To make it more efficient, I am looking for a way to automate the creation of uptime for our different environments. The solution would be to inject JSON files with monitoring points imported to uptime kuma at time of creation.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @DoNnMyTh on GitHub (Nov 5, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description I would like to have a way with which i can create a pipeline or some other way to add monitoring probes. ### ✔️ Solution To make it more efficient, I am looking for a way to automate the creation of uptime for our different environments. The solution would be to inject JSON files with monitoring points imported to uptime kuma at time of creation. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:deployment

labels

2026-02-28 01:49:42 -05:00

deekerman commented

2026-02-28 01:49:44 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 5, 2021):

So, I have considered K8S native deployment before. Reading labels akin to how Prometheus does to figure out what to/how often to monitor would very likely be the best way to monitor in kubernetes. Unfortunately, that is rather far down the line. While I will be happy to do the work for it, UK is < 6 Months old, and I don't want to even start working on features for that until we have a stable feature-set. (Assuming Louis is OK with native k8s monitoring getting added at all).

As for the importing of JSON on startup, that's a duplicate of #270.

@deefdragon commented on GitHub (Nov 5, 2021): So, I have considered K8S native deployment before. Reading labels akin to how Prometheus does to figure out what to/how often to monitor would very likely be the best way to monitor in kubernetes. Unfortunately, that is rather far down the line. While I will be happy to do the work for it, UK is < 6 Months old, and I don't want to even _start_ working on features for that until we have a stable feature-set. (Assuming Louis is OK with native k8s monitoring getting added at all). As for the importing of JSON on startup, that's a duplicate of #270.

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@DoNnMyTh commented on GitHub (Nov 5, 2021):

I don't want to monitor k8s services (as of now, as we use NewRelic/Datadog for it). What I want to have is an automated way with which when we are deploring new environment I can automate the deployment of uptime kuma to monitor service health endpoints

@DoNnMyTh commented on GitHub (Nov 5, 2021): I don't want to monitor k8s services (as of now, as we use NewRelic/Datadog for it). What I want to have is an automated way with which when we are deploring new environment I can automate the deployment of uptime kuma to monitor service health endpoints

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 5, 2021):

So you have N environments, and for each one want to have a separate Kuma instance that gets deployed along with everything else, which then monitors health endpoints for that specific environment?

Edit: Unfortunately, regardless of the answer, I think my original comment still applies. Native k8s is far down the line, and currently, support of importing on startup is a duplicate of 270.

@deefdragon commented on GitHub (Nov 5, 2021): So you have N environments, and for each one want to have a separate Kuma instance that gets deployed along with everything else, which then monitors health endpoints for that specific environment? Edit: Unfortunately, regardless of the answer, I think my original comment still applies. Native k8s is far down the line, and currently, support of importing on startup is a duplicate of 270.

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@DoNnMyTh commented on GitHub (Nov 5, 2021):

Ok, I'll wait for official K8s support.......

@DoNnMyTh commented on GitHub (Nov 5, 2021): Ok, I'll wait for official K8s support.......

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@Richard87 commented on GitHub (Nov 18, 2021):

Hi!

I have alot of domains I want to monitor, and would love to use Uptime-Kuma would you appreciate a PR that adds this feature?

I am proposing a CLI command that I can execute that will find all ingresses with the annotation: uptime-kuma.ingress.kubernetes.io/monitor: true and a optionall argument "--include-ingresses-from-namespaces=default,kuma,superfancy" etc.

@Richard87 commented on GitHub (Nov 18, 2021): Hi! I have alot of domains I want to monitor, and would love to use Uptime-Kuma would you appreciate a PR that adds this feature? I am proposing a CLI command that I can execute that will find all ingresses with the annotation: `uptime-kuma.ingress.kubernetes.io/monitor: true` and a optionall argument "--include-ingresses-from-namespaces=default,kuma,superfancy" etc.

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@Richard87 commented on GitHub (Nov 18, 2021):

Here is a script I made "map-ingress.js":

"It works on my computer", but it needs to restart the server after loading, to start the monitors.
It should also work out of the box on kubernetes, and use the default application credentials (just make sure it has access to list ingresses in the required namespaces.

Todo:

I will also add the ingresses to different groups (All ingresse, NamespaceX)
It should be included in the server.js as a job to monitor for new ingresses on demand

@deefdragon, do you have any advice how a script can trigger UK to refresh the list of monitors? Does the script has a future inside of UK, or should it just exist as a extra tool? :)

@Richard87 commented on GitHub (Nov 18, 2021): Here is a script I made "map-ingress.js": "It works on my computer", but it needs to restart the server after loading, to start the monitors. It should also work out of the box on kubernetes, and use the default application credentials (just make sure it has access to list ingresses in the required namespaces. Todo: - [x] I will also add the ingresses to different groups (All ingresse, NamespaceX) - [ ] It should be included in the server.js as a job to monitor for new ingresses on demand @deefdragon, do you have any advice how a script can trigger UK to refresh the list of monitors? Does the script has a future inside of UK, or should it just exist as a extra tool? :)

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@travisghansen commented on GitHub (Apr 10, 2022):

Ideal for my team would be integration with this: https://github.com/stakater/IngressMonitorController

This would allow us to use a common interface for external services and internal services alike when used in conjunction with this project.

@travisghansen commented on GitHub (Apr 10, 2022): Ideal for my team would be integration with this: https://github.com/stakater/IngressMonitorController This would allow us to use a common interface for external services and internal services alike when used in conjunction with this project.

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@travisghansen commented on GitHub (Apr 10, 2022):

Or even a provider for https://crossplane.io/

@travisghansen commented on GitHub (Apr 10, 2022): Or even a provider for https://crossplane.io/

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@xakraz commented on GitHub (Jul 7, 2025):

What about https://github.com/SQuent/kuma-ingress-watcher ?

@xakraz commented on GitHub (Jul 7, 2025): What about https://github.com/SQuent/kuma-ingress-watcher ?

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 7, 2025):

Or this https://github.com/BigBoot/AutoKuma which solves the same issue I think

@CommanderStorm commented on GitHub (Jul 7, 2025): Or this https://github.com/BigBoot/AutoKuma which solves the same issue I think

deekerman commented

2026-02-28 01:49:47 -05:00

Author

Owner

@hypery2k commented on GitHub (Oct 25, 2025):

When comparing to cronitor i think the cleanest solution whould be an operator for kuma. You then have the ability to listen for resource creation and could directly create monitors, e.g. for CronJobs and Service Monitors.

@hypery2k commented on GitHub (Oct 25, 2025): When comparing to [cronitor](https://github.com/cronitorio/cronitor-kubernetes) i think the cleanest solution whould be an operator for kuma. You then have the ability to listen for resource creation and could directly create monitors, e.g. for CronJobs and Service Monitors.