News for hackers. Stuff that matters.
Re:Announcing the OpenFaaS Function Store by perlgeek on Thursday December 14, 2017 @10:20AM (#15922899)
Not at all. Let's say you manage 100 machines, possibly for different domains, and each generates their own certs. Now you probably want monitoring that alerts you when the certificate is about to expire in the next 20 days (you can renew them 30 days before they expire, without running into rate limit shenanigans).

With 100 servers, you'll have on average about two calendar entries per day, most of which are no-ops, because the certificate renewal worked fine.

Re:Announcing the OpenFaaS Function Store by lkerrekfjk on Thursday December 14, 2017 @10:25AM (#15922950)
You certainly do not need "infinite scaling" to do that. Just a queue of workers running on a dumb server or even just a crontab... Yes it is the very definition of over engineering.
Re:Announcing the OpenFaaS Function Store by perlgeek on Thursday December 14, 2017 @10:26AM (#15922962)
No, you don't need "infinite scaling" for just that. But if you have a FaaS-Setup anyway, you might as well reuse it for such relatively simple (but still useful) tasks.
Re:Announcing the OpenFaaS Function Store by icebraining on Thursday December 14, 2017 @11:31AM (#15923576)
A full Linux kernel and cron daemon for that? You could run it on an ESP32!
Re:Announcing the OpenFaaS Function Store by stephenr on Thursday December 14, 2017 @11:34AM (#15923604)
You know that LE will email you if a cert isn't automatically renewed, right?
Re:Announcing the OpenFaaS Function Store by detaro on Thursday December 14, 2017 @12:13PM (#15924104)
Anecdotally, the case of "certificate renewed, but setup not properly configured to reload all services afterwards" happens quite a bit.
Re:Announcing the OpenFaaS Function Store by inopinatus on Thursday December 14, 2017 @02:05PM (#15925658)
See also: updating vulnerable library packages but not restarting dependent daemons.