-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support supercronic as scheduler #288
Comments
As far as I understand supercronic needs a crontab file. When you configure resticprofile with: global:
scheduler: crond It expects an executable to manage the crontab file, its interface is:
So with a small adapter like #!/bin/sh
CRONTAB=/opt/crontab.txt
if [ "$1" == "-l" ] && [ -f "$CRONTAB" ] ; then
cat "$CRONTAB"
elif [ "$1" == "-" ] ; then
cat - > "$CRONTAB"
fi |
We could also add support to specify a crontab file since all is already in place we just use the |
Relying on crontab might provide two challenges for us:
A solution where we could freely specify the target location for the generated contab file, would allow storing the file on an ephemeral volume. If I am not mistaken, this would allow generating the contab file content with |
I should have read you first comment completely. The wrapper replaces the crontab binary, so I don't need to set a suid flag and won't run into problems with the read-only file system. I can work with that :) I still feel it might be nice to have direct support for supercronic on the long run, so that people can benefit from it out of the box. Thank you for your quick response! |
The |
Btw. I'm updating the
|
Awesome news! Much appreciated! |
I am trying to run Resticprofile on Openshift.
Our compliance (enforced by kyverno) requires us to run payloads with unprivileged user permissions and no privilege escalation, which seem to make it impossible to run
crond
inside an alpine container. The same is true for systemd.supercronic on the other hand runs cronjobs for the current user (including unprivileged users), its file format is basically the know cron format.
Please add support for supercronic, so that users that find themselves in a situation where they need to meet specific compliance challenges can use this wonderful tool as well :)
The text was updated successfully, but these errors were encountered: