Cronicle VS OpenFaaS

Wasn't it simpler to use Cronicle (https://github.com/jhuckaby/Cronicle)?

You can give cronicle a try. It has a web based UI and sone good stats.

Have a look at Cronicle ( https://github.com/jhuckaby/Cronicle )

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Also check out http://cronicle.net/

Would recommend https://github.com/jhuckaby/Cronicle for anyone running cronjobs but would like to have an interface. It has plenty of features, logs, resource stats, and notifications. Plus it's easy to setup.

Thought I'd post here before taking a dive into this and see if anyone has any practical experience. I'm looking for centralising scheduled tasks for multiple servers, preferably with a management GUI for friendliness. I found Crontab-UI which seems to only interact with the single host's crontab. Then I stumbled upon Cronicle which looks feature rich but looks like multi-server is handled by deploying the GUI to each host. A central server + agents on each host would be nicer. I'm wondering if anyone uses Cronicle, or another solution? Thanks!

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenFaaS

Did you consider running knative or openfaas? https://github.com/openfaas/faas

Anyone knows other alternatives for Azure Functions, but for DIY hosting? ( eg. OpenFaas - https://www.openfaas.com/ )

Maybe OpenFaaS with grafana and slack notifications for non-200 responses?

OpenFaaS - https://www.openfaas.com

By the way, if your organization is leveraging EKS as a platform and your DevOps team is willing to enable this operator, there's an exciting tool called OpenFaaS. Essentially, it enables you to host your Lambda functions on your own infrastructure instead of relying on the public cloud provider.

This is where I see K8S coming in – teachers can provide dev deployments that are setup for students to learn. Teachers can also provide containers that run automated tests against the student containers for assessment! Plus, we can smooth over some of the git workflow stuff for the ripest of beginners; we can integrate with github to sync their work on our platform to repositories on their github account, so that they can really take ownership of the work they do on the platform. Last, students can graduate their work from development into production very easily, since we can take the base images + student diffs, build a new "prod" image for the student. We can run students' prod work on "serverless" K8S frameworks like fission or OpenFaas to be able to host many low-traffic "production" apps at the same time.