Issue with Tunnel Binding and ConfigMap in Different Namespaces

[stiliajohny]

I have deployed the ClusterTunnel in the default namespace, while the TunnelBinding resources are deployed in the same namespaces as the respective services. However, the ConfigMap for the ClusterTunnel is located in the default namespace, and the TunnelBinding resources are unable to find it. As a result, I believe the services are not being properly served through the tunnel.

Is there a way to reference the ConfigMap across namespaces or another solution to ensure the TunnelBinding can correctly access it?
Or what is an alternative solution for that?

[adyanth]

Could you post your config yaml here? The tunnel binding does not need to access the configmaps, only the operator needs to be able to access both the configmaps and the tunnel binding.