-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
High
-
2019 Week 29-31, 2019 Week 32-34
Today the Kogito Operator is structured based on generated code from operator-sdk. For simple requirements and resources, this approach is fine. But now with many features coming for the next Kogito releases, there's room for improvements like:
- Isolate Kubernetes API handling
- Define a Reconcile flow
- Increase the number of unit tests
- Document the possible use cases
- Isolate boilerplace code
- is related to
-
KOGITO-94 Integrate Infinispan Operator with Kogito Data Index controller
-
- Closed
-
-
KOGITO-107 Kogito Operator is not reconciling builds
-
- Resolved
-
-
KOGITO-137 Refactoring on resources update in the Kogito Operator controller
-
- Resolved
-
- relates to
-
KOGITO-69 Guideline documentation to help others to contribute to the operator project
-
- Closed
-
