Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1156

Knative integration in SonataFlow Operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • orchestrator-sonataflow

      This story is created to keep track of the tasks needed to integrative Knative services in the SonataFlow Operator, which are managed in github.

          1.
          		 Convert the Knative properties to immutable properties in deployment #371 Sub-task Closed Undefined Jianrong Zhang
          2.
          		 Create knative resources for DataIndex and JobService #368 Sub-task ON_QA Undefined Jianrong Zhang
          3.
          		 Creation of Knative Sinks in SonataFlow CRD #370 Sub-task In Progress Undefined Gabriel Farache
          4.
          		 Knative should not be required to install and run the SonataFlow Operator to deploy workflows Sub-task ON_QA Undefined Jianrong Zhang
          5.
          		 Enhance error messages in SonataFlowPlatform CR status for knative integration Sub-task ON_QA Undefined Jianrong Zhang
          6.
          		 Make Knative optional for SonataFlow Operator deployment Sub-task ON_QA Undefined Jianrong Zhang
          7.
          		 Knative Broker is required even if is not defined in SonataFlow or SonataFlowPlatform Sub-task ON_QA Undefined Jianrong Zhang
          8.
          		 [Bug fix]Serverless workflow pod gets restarted repeatedly after Knative K_SINK injection Sub-task ON_QA Undefined Jianrong Zhang

              jianrzha@redhat.com Jianrong Zhang
              jianrzha@redhat.com Jianrong Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: