Prototype UX for dual interfaces: CLI & K8s Object Spec

Question

Prototype UX for dual interfaces: CLI & K8s Object Spec

kenazk opened this issue 6 years ago · 5 comments

We will support multiple interfaces for using Lyra, starting with a CLI version and a K8s object spec.

We should do some investigation on how these interfaces will work with each other. Additionally, we may want the CLI options for deploying the controller to Kubernetes.

Supports #37.

Answer 1 · 2019-01-21T15:56:18.000Z

I'm interpreting this to mean:

"As a [user of lyra†], I need to apply workflows directly from my workstation to the target infrastructure platform(s) so that
+ The feedback loop is short"
+ I don't need to faff with k8s for 'hello, world'"

"As a [user of lyra‡], I want to apply workflows via kubectl so that
* I get the benefits of a k8s object lifecycle"
* [etc]"

Accurate?

† = I think the 'producer' of workflows is the primary user of the Lyra CLI for these operations.
‡ = And here, the 'consumer' of workflows is more likely to instantiate workflows someone else has made available to them in their cluster(s).

Answer 2 · 2019-01-22T22:43:36.000Z

Yes, thanks for articulating it that way. How does Lyra support both of those interfaces with a common set of functionality?

Answer 3 · 2019-01-28T17:58:16.000Z

@scottyw Given that Tiller is going away, can we make an assertion that we'll use the same lyra library for both CLI and Controller workflows?

Answer 4 · 2019-01-28T19:42:39.000Z

I'm less concerned with the CLI workflow. I'm thinking more about the K8s workflow. How do you want to structure the K8s object spec? This is what @scottyw started with: apiVersion: lyra.example.com/v1alpha1 kind: Workflow metadata: name: sample2-workflow spec: workflowName: "sample2" data: foo: kubeFooooo2 bar: kubeBaaaar baz: kubeBaaaaz refreshTime: 35 If that seems fine, then I think it's just documenting the prescribed workflow in the repo. Kenaz

…

On Mon, Jan 28, 2019 at 6:48 AM JD Welch ***@***.***> wrote: What specific question do you have? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABag6f0OzLjzPcZsEH_4EthPDGm5un70ks5vHw3FgaJpZM4aGato> .

Answer 5 · 2019-01-29T10:42:10.000Z

@kenazk I think we're using the same library both ways. Lyra won't need to run in Kube but we'll likely eventually support it for those who want it.