<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">><br>
> What is the result of this discussion ?<br>
<br>
</span>I think the result is that we need to have a meeting over cross tenancy and how it should be applied.<br>
<br></blockquote><div><br></div><div>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.</div><div><br></div><div>Is there any change on this since that meeting ?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Supporting cross-tenancy is a fairly large architectural change and should be affecting multiple components.<br>
<br></blockquote><div><br></div><div>Multiple components beyond Metrics / Alerts or the security filters ? Can you ellaborate this, please ?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
At the very least we need to discuss how to properly handle it with regards to security integration with OpenShift.<br>
<span class=""><br></span></blockquote><div><br></div><div>Yes. Please, could you prepare some info you would need from Alerting component ?</div><div>I.e. tenant formats or other related info different from the current logic.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> Do you want any additional enhancement around this ?<br>
><br>
> I can see two potential actions:<br>
> - Perhaps to move the /admin endpoint prefix to /tenants to align with the<br>
> same in metrics.<br>
<br>
</span>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.<br></blockquote><div><br></div><div>The /tenants endpoint provides all the tenants of the system.</div><div>That was why in the previous meeting we proposed the /admin endpoint.</div><div><br></div><div>Renaming and endpoint is not a problem but as this is already released we are going to maintain it for backwards compatibility.</div><div>(And we can mark it as deprecated for following versions).</div><div><br></div><div>Suggestions for other names are welcome.</div><div><br></div><div>Please, lets move on this, as this feature is important for Alerting users.</div><div><br></div><div>Lucas</div></div></div></div>