mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
Adding breaking change for the removal of legacy multitenancy (#83870)
* Adding breaking change about the removal of legacy multitenancy * Update docs/migration/migrate_8_0.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
This commit is contained in:
parent
b42da051ef
commit
a5b02c9957
1 changed files with 6 additions and 0 deletions
|
@ -36,6 +36,12 @@ for example, `logstash-*`.
|
|||
=== Settings changes
|
||||
|
||||
// tag::notable-breaking-changes[]
|
||||
[float]
|
||||
==== Multitenancy by changing `kibana.index` is no longer supported
|
||||
*Details:* `kibana.index`, `xpack.reporting.index` and `xpack.task_manager.index` can no longer be specified.
|
||||
|
||||
*Impact:* Users who relied on changing these settings to achieve multitenancy should use *Spaces*, cross-cluster replication, or cross-cluster search instead. To migrate to *Spaces*, users are encouraged to use saved object management to export their saved objects from a tenant into the default tenant in a space. Improvements are planned to improve on this workflow. See https://github.com/elastic/kibana/issues/82020 for more details.
|
||||
|
||||
[float]
|
||||
==== Legacy browsers are now rejected by default
|
||||
*Details:* `csp.strict` is now enabled by default, so Kibana will fail to load for older, legacy browsers that do not enforce basic Content Security Policy protections - notably Internet Explorer 11.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue