Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-128

Operator support on Kubernetes for deploying Kogito Runtimes

    XMLWordPrintable

Details

    • 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)

    Description

      Nowadays the Kogito Operator only work on OpenShift for a couple reasons:

      1. Relies on BuildConfig for s2i
      2. Uses DeploymentConfig to handle pods rollouts
      3. Relies on ImageStreamTag to coordinate the deployed images
      4. Creates Routes based on DeploymentConfig

      For the Kogito Operator to work on Kube, the way it's deploying the application should be redesigned (or at least create a new deployment strategy when running on Kube).

      The images should be revisited as well. Might not work on Kube duo to s2i capabilities.

      For the community point of view, having the Operator to work on Kubernetes will make it very easy for developers to try it locally since there's a lot of options for running Kubenertes in a lightweight way.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users KOGITO-1999 Separate build tasks on Kogito Operator to a new CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-1654 Guide for Core/Runtimes team to Smoke test local changes on CRC

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-1998 Deprecate KogitoApp CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-2064 Review Kogito CLI deploy command to deploy a Runtime and a Build CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          causes

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-2278 KogitoRuntime cannot start application from image in insecure registry

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users KOGITO-1999 Separate build tasks on Kogito Operator to a new CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-1940 Use services instead routes to inner communication between Kogito services

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-2087 BDD tests: KogitoRuntime Support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-2327 BDD tests: KogitoRuntime Support in Kubernetes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-2404 Avoid to register Openshift components when running in Kubernetes

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-1998 Deprecate KogitoApp CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-2046 Remove "infinispan properties module" from Data Index and Jobs Service images

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-1488 Operator should support default Spring Boot health check in probes

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-2269 Include Kogito Operator example images in the Operator Release Cycle

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-247 Improve Operator for Native build to enable quicker access

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. KOGITO-952 Research on splitting KogitoApp into KogitoRuntimes and KogitoBuild

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              rhn-support-zanini Ricardo Zanini Fernandes
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: