ScheduledWorkflow CRD: CLI

[ynqa]

Will it prepare the scheduledworkflows' CLIs in this repository to manage controller like argo? Or adding subcommands to argo.

[vicaire]

It will be done in this repo. Thanks!

[ynqa]

@vicaire Already done to make CLI? If it has not started yet, I'll make it!

[vicaire]

Sure, could you make a proposal of how it will look like?

It would be nice if it could take as a parameter a file with an Argo workflow, and automatically generate the yaml for the ScheduledWorkflow.

[ynqa]

@vicaire First, I'll make a command for installation of controller and CRD like argo install. Then, scheduledworkflow controller is deployed as Deployment to kubernetes.

[vicaire]

That looks great!

[jlewi]

Why do we need a CLI to install the CRD? Why can't it just be installed as ksonnet package like all the other components in the registry?

Using a CLI to install the controllers goes against the idea in K8s of managing infrastructure decoratively using config.

I also don't think it would scale very well; e.g. having individual CLI's for every CRD in Kubeflow and forcing the user to install each one would be unwieldy.

[ynqa]

@jlewi First, I think CLI to manage scheduledworkflows should be prepared. For example, for dealing with the case to continue execution of the Argo workflow where it left off (or by indicating arbitrary position). I think it's troublesome to handle this by kubectl and the manifests only.

And also I don't think it's strange to install the components (CRD/controller) into k8s using this CLI owing to consistency of operations.

But I agreed your opinions too. So I'll commit except for CLIs (I think there is no rush to prepare CLI itself) in #12 PR.

[vicaire]

For installation of the CRD, we indeed need to conform to the Kubeflow standard of using a ksonnet package.

Thanks for the reminder @jlewi.

[ynqa]

I got it. Thanks.