1. Proposed title of this feature request

• Request for namespace-bound Serverless support in multi-mesh cluster setup

2. What is the nature and description of the request?

In a multi-tenant RHOCP cluster environments, where:

• Several "RHOCP consumer projects" - composed by several (i.e. dev, pre-prod, prod) namespaces
• And those several namespaces are are members of a dedicated an a dedicated ServiceMeshControlPlane (for isolation purposes)

As an RHOCP cluster administrator, the customer would like option to enable Serverless capabilities on a per-namespace basis.

• NOTE: in the current context, Serverless workload is required to be bound to one, single specific mesh, as highlighted [0] in the "Integrating Service Mesh with OpenShift Serverless section of the documentation.

3. Why does the customer need this? (List the business requirements here)

• Specific projects are bound to specific clusters and they would need Serverless capabilities as an opt-in option.

[0]

"The mesh that Serverless is part of must be distinct and preferably reserved only for Serverless workloads. That is because additional configuration, such as Gateways, might interfere with the Serverless gateways knative-local-gateway and knative-ingress-gateway. Red Hat OpenShift Service Mesh only allows one Gateway to claim a wildcard host binding (hosts: ["*"]) on the same port (port: 443). If another Gateway is already binding this configuration, a separate mesh has to be created for Serverless workloads."