-
Feature Request
-
Resolution: Done
-
Major
-
0.3.0
-
None
-
2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18)
Today we depend on the user to manually deploy the Strimzi Operator and install Kafka cluster and topics with it.
This enhancement is to add the following feature
1. Add the option to create Kogito operator with dependency on the Strimzi Operator.
2. Add a new Spec ".Spec.Kafka.Instance" that's the name of the Kafka instance.
3. Update CLI
This enhancement is also to add this feature to the Kogito Data Index controller, so the operator will:
1. If user specifies the Kafka ExternalURI ".Spec.Kafka.ExternalURI", the value will be used by the data index service.
2. Otherwise, check if the Strimzi APIs are supported in the cluster. If Strimzi APIs are supported:
2.1. Create the KafkaTopic CRs.
2.2. If the user specifies the Kafka Instance ".Spec.Kafka.Instance", use the URI of the instance for the data index service. The number of replicas of the KafkaTopic can be extracted from the Kafka instance.
2.3. If the Kafka Instance is not specified, try to find a Kafka instance that is created in the namespace, and use its URI. The number of replicas of the KafkaTopic can be extracted from the Kafka instance.
2.4 Abort the deployment if no Kafka instance is installed
- blocks
-
KOGITO-614 Operator to deploy Kafka for Data Index service
- Resolved
- is related to
-
KOGITO-614 Operator to deploy Kafka for Data Index service
- Resolved
-
KOGITO-613 Add a init container to Data Index to check for Infinispan and Kafka before starting
- Closed
-
KOGITO-601 Refactor Data Index to use RHSysUtils
- Resolved
-
KOGITO-458 Add health check for Data Index service
- Closed
- relates to
-
KOGITO-195 Researshing on integrating Infinispan Operator with Kogito Operator
- Resolved
-
KOGITO-222 Kogito Operator to deploy Data Index Service
- Resolved