-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Button to manually trigger a cronjob #7968
Comments
I first thought this could have been implement as a resource action, such as the ones we already have for Deployment resources. But to trigger a Cronjob in K8s requires creating a new Due to this constraints, I'm not sure this is something we could/should implement in Argo CD. But I'm happy to pick up the discussion. |
Just wanted to bump this for visibility and let you know this is still desperately needed. |
Yes, that would be very useful. Lens UI already has this implemented and it's very handy. |
FYI in case anyone else crosses this bridge: argo workflows has a much better management interface and RBAC for jobs. It works out of the box and uses a separate permission set that adheres more closely to the use case. |
@taylorsmithgg can you put here a link to that argo workflows feature? |
@terrytangyuan thanks. |
CronWorkflow is not meant to be manually triggered. You can save the workflow spec into a WorkflowTemplate and submit it from the UI. |
@terrytangyuan ok got it thanks :) |
An upvote for this feature |
That feature would really be VERY useful |
Closing in favor of duplicate #4116 I also like this idea. :-) |
Summary
It would be extremely useful to have the ability to manually trigger cronjobs after a sync is sucessful.
Motivation
Our developers are currently pushing cronjobs with argo, but do not have an immediate way to test them and verify. They have to either manually request our assistance to trigger them or wait until the schedule triggers.
Even if we allowed devs to delete/recreate or force, there are no patterns to also create a manual trigger in the process today.
Proposal
An additional button in the UI would be great.
We (admins) are currently using k9s to do this.
The text was updated successfully, but these errors were encountered: