masayag opened a new issue, #2031: URL: https://github.com/apache/incubator-kie-kogito-apps/issues/2031
### Description In a cloud environment when a workflow is deployed via a sonataflow CR, the identity of a workflow in the context of a k8s cluster is determined by a combination of the workflow's name and namespace. However, in the Data-Index, there is no concept of a namespace of a workflow. This might lead to a problem when deploying two workflows on the same cluster into different namespaces. Having supported the SonataflowClusterPlatform as a method to create a global Data-index that expands over the cluster, we might hit a situation in which two (or more) workflows with the same name will be deployed successfully in their namespace, however only the later workflow definition will be available in the Data-Index. The implication in this case is not being able to view/list/track workflows from other namespaces via the Data-index, and if relying on the Data-index to expose the endpoint for the workflow, the target workflow might be the undesired one. A similar issue is reported to the operator: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/442 ### Implementation ideas _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
