Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-48

[deliverable][use case] Workflow API on OpenShift (CRD) (community only)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • 1.27.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 2022 Week 41-43 (from Oct 10), 2022 Week 44-46 (from Oct 31), 2022 Week 47-49 (from Nov 21), 2022 Week 50-02 (from Dec 12), 2023 Week 03-05 (from Jan 16), 2023 Week 06-08 (from Feb 6)

      Motivation

      Add a representation of the Serverless Workflow implementation on OpenShift clusters. Users can create a YAML file representation of a workflow definition per the specification and apply it to OpenShift clusters.

      Goals

      An operator is responsible for handling this definition and deploying a Knative Service representation of the workflow runtime engine.

      In this first version, users are supposed to:

      1. Create Custom Resource representing a workflow definition
      2. Have the controller build an image for the given service representation
      3. Have the controller deploy a Knative Service

      Not all Workflow features will be supported in this first version.

      The features supported in the first versions are the following:

      • Functions
      • States
        • Supported State types:
          • Switch including dataConditions
          • Inject including data with a transition
          • Operation including Actions with functionRef with arguments
      • KeepActive
      • AutoRetries
      • ExpressionsLang (jq or jsonpath)

      Non-goals

      • This first version won't be productized, release will be done on OperatorHUB only following an announcement in the community.

            dsalerno@redhat.com Davide Salerno
            rhn-support-zanini Ricardo Zanini Fernandes
            Tristan Radisson Tristan Radisson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: