Uploaded image for project: 'OpenShift Migration Toolkit for Containers'
  1. OpenShift Migration Toolkit for Containers
  2. MIG-942

Crane pipelines with hello crane example

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Crane alpha2
    • None
    • MTRHO
    • Sprint 210

      Through conversations around community support of the usage of crane, we feel there's value in providing some kind of "crane install" for a cluster. It's a little awkward to say "crane install" in the context of a cluster, since crane itself is a cli. But there is probably some amount of utility in us providing an install of some kind (simple manifest file you kubectl create, kustomizable template, or helm chart), that will set up a cluster so that it's ready to run crane pipelines.

      Let's assume that Tekton is already set up in the cluster. In the crane-runner repo, we can include a few things:

      • The installation artifacts that are responsible for adding the crane pipeline tasks (export/transform/load), as well as potentially an example Pipeline.
      • An example hello-crane workload, and associated pipeline that will migrate that workload from one namespace to another. Users may optionally use to see crane do something useful in their cluster.
      • Documentation that describes crane-runner,  "crane pipelines" if that's what we want to call the collection of value that we're offering with the pipeline artifacts, and basic instructions for how to run hello crane using the pipeline and the example workload. Should be submitted to https://github.com/konveyor/crane-documentation, which is crane's main upstream docs repo.

      Let's keep it simple, so that if there is no necessity for templating or helm, we can just stick to a simple manifest file that the user can oc create.

              rh-ee-dzager David Zager
              ernelson@redhat.com Erik Nelson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: