• False
    • False
    • ToDo
    • undefined
    • Sprint 210

      A lot of discussions are ongoing around how the Crane 2 UI might look when integrated into the OCP console using the dynamic plugin APIs. For this story, we're looking to build a POC to prove out how a next-gen Crane/MTC 2 UI will look, learn how it can integrate with the OCP console, and what limitations exist that we'll need to work within.

      For this deliverable, we're looking for a demoable POC that is a "hello world" dynamic plugin. We'd like to lay the foundation for what the front-end stack looks like so this can be picked up by someone other than Ian and we can build on top of that. Since we expect the initial Crane 2 UI to probably be a wizard that builds up a Tekton Pipeline, let's experiment getting something that looks like that.

      Some questions to answer:

      • Can we establish an architecture that actually uses websockets to watch a CRD API surface?
      • Is there a better alternative to a react-saga based data layer? (react query?)
      • What can you actually do with the OCP dynamic plugin API at this point?

              ibolton@redhat.com Ian Bolton
              ernelson@redhat.com Erik Nelson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: