[DOCS] Adds breaking changes for 7.11 (#87947)

* [DOCS] Adds breaking changes for 7.11

* [DOCS] Fixes typo

* [DOCS] Adds release tag
This commit is contained in:
gchaps 2021-01-13 11:16:46 -08:00 committed by GitHub
parent d3e231be2b
commit 6ef0556877
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 45 additions and 0 deletions

View file

@ -6,6 +6,7 @@
This section discusses the changes that you need to be aware of when migrating
your application from one version of Kibana to another.
* <<breaking-changes-7.11, Breaking changes in 7.11>>
* <<breaking-changes-7.10, Breaking changes in 7.10>>
* <<breaking-changes-7.9, Breaking changes in 7.9>>
* <<breaking-changes-7.8, Breaking changes in 7.8>>
@ -21,6 +22,7 @@ your application from one version of Kibana to another.
See also <<whats-new>> and <<release-notes>>.
--
include::migration/migrate_7_11.asciidoc[]
include::migration/migrate_7_10.asciidoc[]
include::migration/migrate_7_9.asciidoc[]
include::migration/migrate_7_8.asciidoc[]

View file

@ -0,0 +1,43 @@
[[breaking-changes-7.11]]
== Breaking changes in 7.11
++++
<titleabbrev>7.11</titleabbrev>
++++
coming::[7.11.0]
This page discusses the breaking changes that you need to be aware of when migrating
your application to {kib} 7.11.
// The following section is re-used in the Installation and Upgrade Guide
// tag::notable-breaking-changes[]
[discrete]
[[ingestManager_renamed_fleet]]
=== Ingest Manager plugin renamed Fleet
*Details:* The `ingestManager` plugin has been renamed `fleet`.
*Impact*:
* The app url change from /app/ingestManager to /app/fleet.
* The privilege `feature_ingestManager.*` is not valid anymore and should be replaced by `feature_fleet.*`.
*via https://github.com/elastic/kibana/pull/83200[#83200]*
[discrete]
[[reporting_plugin]]
=== Reporting plugin added new validation for protocol
*Details:* The Reporting plugin added new validation for protocol strings in Network Policy configurations.
*Impact*: See <<reporting-network-policy, Restrict requests with a Reporting network policy>>.
If the kibana.yml has a Reporting network policy before upgrade,
the protocol strings must end with a colon. Otherwise, config validation
will fail and Kibana will not start.
*via https://github.com/elastic/kibana/pull/80766[#80766]*
// end::notable-breaking-changes[]