-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAC] Turn off RAC features for those using multi tenancy #108393
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
Note: the way to access the |
Suggestion for the unsafe flag: |
Sorry for being late with this question, but if
what's the plan for https://kibana.siem.estc.dev? Are we completely moving away from multi-tenant envs, there is a plan for rebuilding https://kibana.siem.estc.dev and there is (will be) a guideline for users how to do a similar migration for their own environments? |
It's a good question, but I don't think I have a good answer 😬 In Observability we similarly have shared clusters, and we've historically used |
Summary
When a user has the
kibana.index
config value set a custom index is written to. We originally wanted to support multi tenancy for RAC via thexpack.ruleRegistry.index
setting.However, it has become hard to reason about this with three methods of accessing data (the rule data client, the alerts data client, and the timeline search strategy), and RBAC layered on top.
Various discussions have happened, e.g. #106432 and #104958 but it's still unclear how to provide this in a non-buggy / bulletproof way. @jasonrhodes and I had discussed a temporary workaround, but it would only fix things for the rule data client and the search strategy. There is work planned to land in 7.15 which uses the alerts data client.
This ticket would instead implement the following:
kibana.index
is setUNSAFE_multi_tenancy_alerting
kibana.index
is set, we turn everything offWith both settings the user would receive the behaviour as it stands now, in a non segmented form.
The text was updated successfully, but these errors were encountered: