EPIC - Support the same workflow name in different namespaces

[wmedvede]

Description

From the SonataFlow and other k8s deployments perspective, a workflow/process with the same name, deployed in two different namespaces, namespace1 and namespace2, represents a completely different workflow/process. And, even while having the same name/id, the workflow/process definition might be totally different.

However, when we have an installation, where the Data Index was installed in a cluster-wide mode, we have an issue, since the Data Index is not prepared to manage namespaced workflow/process definitions.

Instead, if workflow/process "my-workflow" is deployed in namespace1, and then, in a later point in time, in namespace2 (with a potential different definition), the last deployment will overwrite previous definition.

The objective of this epic is to support this use case

• Operator support to handle the same workflow name in different namespaces #442
• Data Index support to handle the same workflow/process name in different namespaces incubator-kie-kogito-apps#2031
• Runtime enhancements to support the same workflow/process definition name in different namespaces incubator-kie-kogito-runtimes#3562
• Serverless Workflow UI enhancements to support the same workflow name in different namespaces incubator-kie-tools#2435

Implementation ideas

No response

[fjtirado]

An alternative to deploy the same workflow with different configuration is to allow dynamic configuraiton within the same namepace for OpenAPI properties, see apache/incubator-kie-kogito-runtimes#3573