[v2] I have to create Listener for each Connector?

[xe-leon]

Is your feature request related to a problem? Please describe.
In v1 I only had to expose service, it will appear on remote cluster automatically (and I could restrict it with SkupperClusterPolicies). It is quite handy.
In v2 I have to create Listener for it. With a large number of clusters this just doubles the work.

Describe the solution you'd like

Create listeners automatically and restrict this behavior with policies.

[grs]

V2 prioritises declarative configuration over the CLI. You have to apply a site record at each site anyway, if you know the service(s) that will be consumed at that site you can apply the appropriate listener resource(s) at the same time. If the service is only known about later, then presumably something at the site needs to be updated to make use of it and the listener could be applied when making that update.

The change in behaviour to make use of service explicit was deliberate for v2 as the v1 behaviour was frequently found undesirable.

[xe-leon]

I appreciate the move to a declarative approach.
Just an example where I don't need to change anything on the site where Listeners located:
I have a large number of clusters with prometheus, all of which need to be available from Grafana, which works in a separate cluster. Ideally, I would just create a connector, and the service would automatically appear in the grafana cluster, which would trigger a kyverno policy that would create a new datasource for it.
May be Listener with some mask or regular expression could be a solution?

[grs]

Thanks for that extra context. We may be able to I can understand the desire for a more automated configuration of remote listeners in response to connectors being defined. I will keep this in mind for future development of v2.