>
> What is the result of this discussion ?

I think the result is that we need to have a meeting over cross tenancy and how it should be applied.

We had one meeting about this and it was discussed that cross tenancy was not requested for Metrics components but it was requested for Alerting.

Is there any change on this since that meeting ?

Supporting cross-tenancy is a fairly large architectural change and should be affecting multiple components.

Multiple components beyond Metrics / Alerts or the security filters ? Can you ellaborate this, please ?

At the very least we need to discuss how to properly handle it with regards to security integration with OpenShift.

Yes. Please, could you prepare some info you would need from Alerting component ?

I.e. tenant formats or other related info different from the current logic.

> Do you want any additional enhancement around this ?
>
> I can see two potential actions:
> - Perhaps to move the /admin endpoint prefix to /tenants to align with the
> same in metrics.

The /tenants endpoint in metrics is not for cross-tenant operations. Its probably not a great idea to to have two endpoints of the same name between components which do different things.

The /tenants endpoint provides all the tenants of the system.

That was why in the previous meeting we proposed the /admin endpoint.

Renaming and endpoint is not a problem but as this is already released we are going to maintain it for backwards compatibility.

(And we can mark it as deprecated for following versions).

Suggestions for other names are welcome.

Please, lets move on this, as this feature is important for Alerting users.

Lucas