Add option to create one-off job from cron job

[muenchdo]

Summary

Add a button to create a one-off job from a cron job.

Motivation

We often deploy cron jobs using Argo CD, but want to do test run of the job after deployment. Using kubectl you can easily create a job from a cron job using kubectl create job --from=cronjob/foo foo. As most of our engineers don't actually have cluster access using kubectl, integrating this into Argo CD (including RBAC, easily browsable logs, etc.) would be tremendously useful.

Proposal

Similar to the Restart option for deployments, this could be included in the dropdown when clicking a cron job object in the resource tree.

[jessesuen]

This isn't currently possible with the current action feature, which only manipulates the resource that you are performing the action on.

However I do see the value in generating new resources as part of an action. This would need to be a new feature and potentially affect RBAC.

[RichiCoder1]

This would be an interesting feature standalone to be able to provide the ability to perform manual, but defined cluster actions via the ArgoCD UI/API

[genslein]

bump here, there is a real desire to run things like seed data migrations as one-off jobs in real environments from the UI.

This unblocks regular deployment pipelines and allows better management of multiple environments. Any updates?

[stephaneetje]

Hello, also very interested in that feature that would simplify a LOT our processes

[crenshaw-dev]

If anyone's willing to put up a PR, I'd be happy to help w/ dev setup and review!

My rough idea of the way this could work is that the custom action could produce a list of manifests (strings of JSON or YAML) and actions (for now just apply, but maybe later delete, etc.). The API server would then loop over that list and send the manifests to the controller to sync. The controller would make sure that the application actually has permissions to deploy the resource.

I'm hazy on the exact mechanic behind "send the manifests to the controller." The API server currently has the ability to trigger and "override" sync, where manifests are sent to the controller to be applied once, ignoring the usual application source of truth. But I'm not sure the override mechanism currently has a "just add this one thing (or these few things)" option. The developer would probably have to build this new sync mechanism.

@jessesuen does that line up with how you'd envision this feature being built?

[reggie-k]

So upon a new "create-from" action, performed on the

apiVersion: batch/v1
kind: CronJob
metadata:
  ...

resource, which is part of some Application, a new

apiVersion: batch/v1
kind: Job
metadata:
  ...

resource (which is not part of that Application) has to be created?

[crenshaw-dev]

@reggie-k yep, something like that is what I'd imagine!

[bygui86]

sorry guys, I don't understand the status of this new feature :)
can someone summarise it?
thanks!!

[SergeyLadutko]

Can i make this button with Lua ?

[bygui86]

@SergeyLadutko very good question! I'm looking into it, but I don't have Lua expertise at the moment :(
Any update here?

[SergeyLadutko]

@bygui86
This is a very important button as it is the last thing that makes our developers use Lens or dashboard