-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
This is already sort of supported. In 2.0, we'll explicitly allow users to use existing Jaeger and Kiali installations. In addition to this, if Jaeger and/or Kiali are enabled and the referenced resource does not exist, the Maistra operator should install one.
If the Maistra operator creates a Jaeger or Kiali resource, it will mark the resource as owned by the SMCP resource and the instance will be deleted when the SMCP resource is deleted. Similarly, if Jaeger or Kiali are disabled in the future and the SMCP resource is the owner, those resources will be deleted.
In any case, the Maistra operator will take ownership of some of the external_services fields in the kiali operator, specifically, url, enabled, and password fields for tracing and grafana, and the password field for prometheus.
- incorporates
-
MAISTRA-1563 Cannot define kiali.resources in SMCP spec
- Closed
-
OSSM-218 Tracing not enabled in kiali when using production-elasticsearch template in SMCP
- Closed
-
MAISTRA-1205 Kiali replicaCount is not passed from SMCP CR
- Closed
-
MAISTRA-1613 Watch for jaeger route asynchronously and enable/disable kiali tracing
- Closed
- relates to
-
MAISTRA-1087 Enable external Jaeger instance to be used by Service Mesh
- Backlog
-
MAISTRA-1065 ServiceMesh operator does not support external ElasticSearch clusters for Jaeger storage
- Backlog