Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-6138 Kogito user-friendly deployment
  3. KOGITO-6294

ProtoBuf ConfigMap should be created on instantiation of KogitoRuntime

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 1.16.1.Final
    • None
    • None
    • None
    • False
    • False
    • 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15), 2021 Week 49-51 (from Dec 6th), 2022 Week 02-04 (from Jan 10), 2022 Week 05-07 (from Jan 31), 2022 Week 08-10 (from Feb 21), 2022 Week 11-13 (from Mar 14), 2022 Week 14-16 (from Apr 4), 2022 Week 17-19 (from Apr 25), 2022 Week 20-22 (from May 16), 2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27), 2022 Week 29-31 (from Jul 18), 2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29), 2022 Week 38-40 (from Sept 19), 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), 2023 Week 09-11 (from Feb 27), 2023 Week 12-14 (from Mar 20)

      In current implementation, Data-Index service scan all KogitoRuntime instance to mount their ProtoBuf Configmap as a volume. If ProtoBuf configMap of any KogitoRuntime not present then Data-Index reconciler create it and then mount it over itself.

      Challenges
      To deprecreate KogitoRuntime, KogitoSupportingService reconciler should not depend on KogitoRuntime instances.

      Solution
      ProtoBuf ConfigMap should be created on instantiation of KogitoRuntime and KogitoSupportService should only responsible to scan all config map of type Protobuf and mount it.

              vajain Vaibhav Jain
              vajain Vaibhav Jain
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: