mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
# Backport This will backport the following commits from `main` to `8.x`: - [(Docs) Add Kibana upgrade notes page (#193268)](https://github.com/elastic/kibana/pull/193268) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-10-07T09:51:42Z","message":"(Docs) Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes and\r\ndeprecations introduced since the last major version. I slightly edited\r\nsome bits to align the wording and add version information to each item,\r\nand took a bit of freedom (not too much!) to ignore items that shouldn't\r\nbe identified as deprecations or breaking changes, or to move them to\r\nthe appropriate section in this page.\r\n- adds a link to the new page from the Upgrade Kibana page.\r\n\r\n<img width=\"1483\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img width=\"810\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm wondering if we should leave this uncategorized or at least identify\r\nwhich items are specific to a solution. It also doesn't make much sense\r\nthat we have Obs here while we don't have Security. Let's think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the page is initially added under the Release notes\r\nsection. I'll need to make sure that this does not interfere with the\r\nrelease notes automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll need update the\r\nrelease notes internal docs to add the relevant information to this page\r\nwith each minor release, or find a way to automate.\r\n\r\nCloses: https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers <lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version"],"title":"Add Kibana upgrade notes page","number":193268,"url":"https://github.com/elastic/kibana/pull/193268","mergeCommit":{"message":"(Docs) Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes and\r\ndeprecations introduced since the last major version. I slightly edited\r\nsome bits to align the wording and add version information to each item,\r\nand took a bit of freedom (not too much!) to ignore items that shouldn't\r\nbe identified as deprecations or breaking changes, or to move them to\r\nthe appropriate section in this page.\r\n- adds a link to the new page from the Upgrade Kibana page.\r\n\r\n<img width=\"1483\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img width=\"810\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm wondering if we should leave this uncategorized or at least identify\r\nwhich items are specific to a solution. It also doesn't make much sense\r\nthat we have Obs here while we don't have Security. Let's think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the page is initially added under the Release notes\r\nsection. I'll need to make sure that this does not interfere with the\r\nrelease notes automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll need update the\r\nrelease notes internal docs to add the relevant information to this page\r\nwith each minor release, or find a way to automate.\r\n\r\nCloses: https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers <lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193268","number":193268,"mergeCommit":{"message":"(Docs) Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes and\r\ndeprecations introduced since the last major version. I slightly edited\r\nsome bits to align the wording and add version information to each item,\r\nand took a bit of freedom (not too much!) to ignore items that shouldn't\r\nbe identified as deprecations or breaking changes, or to move them to\r\nthe appropriate section in this page.\r\n- adds a link to the new page from the Upgrade Kibana page.\r\n\r\n<img width=\"1483\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img width=\"810\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm wondering if we should leave this uncategorized or at least identify\r\nwhich items are specific to a solution. It also doesn't make much sense\r\nthat we have Obs here while we don't have Security. Let's think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the page is initially added under the Release notes\r\nsection. I'll need to make sure that this does not interfere with the\r\nrelease notes automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll need update the\r\nrelease notes internal docs to add the relevant information to this page\r\nwith each minor release, or find a way to automate.\r\n\r\nCloses: https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers <lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
This commit is contained in:
Kibana Machine
GitHub
parent
8139c7bafe
commit
49ec768130
3 changed files with 1724 additions and 89 deletions
|
|
@ -73,6 +73,9 @@ Review important information about the {kib} 8.x releases.
|
|||
|
||||
--
|
||||
|
||||
|
||||
include::upgrade-notes.asciidoc[]
|
||||
|
||||
[[release-notes-8.15.2]]
|
||||
== {kib} 8.15.2
|
||||
|
||||
|
|
@ -119,6 +122,7 @@ Machine Learning::
|
|||
* Fixes link to anomaly detection wizard from pattern analysis in Discover ({kibana-pull}192375[#192375]).
|
||||
* Fixes an issue with the `http_endpoint` input config loading incorrectly in an Automatic Import workflow ({kibana-pull}191964[#191964]).
|
||||
|
||||
|
||||
[[release-notes-8.15.1]]
|
||||
== {kib} 8.15.1
|
||||
|
||||
|
|
@ -241,7 +245,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.15.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-184036]]
|
||||
.Adds rate limiting to install by upload endpoint.
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -660,7 +663,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.14.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-182074]]
|
||||
.Renamed an advanced setting to enable {esql}.
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1111,7 +1113,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.13.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-176879]]
|
||||
.Removes conditional topics for Kafka outputs
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1120,7 +1121,6 @@ The Kafka output no longer supports conditional topics. For more information, re
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-176443]]
|
||||
.Most Fleet installed integrations are now read-only and labelled with a *Managed* tag in the Kibana UI
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1136,7 +1136,6 @@ For more information, refer to ({kibana-pull}172393[#172393]).
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-174674]]
|
||||
.Removes `is_nan`, `is_finite`, and `is_infinite` functions from {esql}
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1512,7 +1511,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.12.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-172224]]
|
||||
.New SLO architecture
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1536,7 +1534,6 @@ Be aware that when installing a new SLO (or after resetting an SLO), we install
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-170635]]
|
||||
.A new sub-feature privilege to control user access to the cases settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -1920,21 +1917,21 @@ Before you upgrade to 8.11.0, review the breaking changes, then mitigate the imp
|
|||
|
||||
|
||||
[discrete]
|
||||
[[breaking-167085]]
|
||||
.Improve config output validation for default output.
|
||||
[%collapsible]
|
||||
====
|
||||
*Details* +
|
||||
Improve config output validation to not allow to defining multiple default outputs in {kib} configuration. For more information, refer to ({kibana-pull}167085[#167085]).
|
||||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-161806]]
|
||||
.Convert filterQuery to KQL.
|
||||
[%collapsible]
|
||||
====
|
||||
*Details* +
|
||||
Converts `filterQuery` to a KQL query string. For more information, refer to ({kibana-pull}161806[#161806]).
|
||||
====
|
||||
|
||||
[float]
|
||||
[[deprecations-8.11.0]]
|
||||
=== Deprecations
|
||||
|
|
@ -2264,7 +2261,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.10.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-162665]]
|
||||
.New summary search capabilities cause existing SLOs to stop working
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2342,7 +2338,6 @@ DELETE .slo-observability.sli-v1*
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-162506]]
|
||||
.Get case metrics APIs now internal
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2351,7 +2346,6 @@ The get case metrics APIs are now internal. For more information, refer to ({kib
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-162492]]
|
||||
.Case limits
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2373,7 +2367,6 @@ For the full list, refer to {kib-issue}146945[#146945].
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-159041]]
|
||||
.`addProcessorDefinition` is removed
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2382,7 +2375,6 @@ The function `addProcessorDefinition` is removed from the Console plugin start c
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-162288]]
|
||||
.The Download CSV endpoint has changed.
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2699,7 +2691,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.9.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-159118]]
|
||||
.Hide Uptime app if no data is available
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -2709,7 +2700,6 @@ For synthetic monitoring, we now recommend to use the new Synthetics app. For mo
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-159012]]
|
||||
.Remove synthetics pattern from Uptime settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3282,7 +3272,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.8.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-155470]]
|
||||
.Removes legacy project monitor API
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3294,7 +3283,6 @@ In 8.8.0 and later, an error appears when you use the project monitor API.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-147985]]
|
||||
.Changes the privileges for alerts and cases
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3799,7 +3787,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.7.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-149482]]
|
||||
.Removes the fields list sampling setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3811,7 +3798,6 @@ In 8.1.0 and later, {kib} uses the field caps API, by default, to determine the
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-146990]]
|
||||
.Removes the legacy pie chart visualization setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3823,7 +3809,6 @@ In 7.14.0 and later, the new aggregation-based pie chart visualization is availa
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-147616]]
|
||||
.Removes the current_upgrades endpoint
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -3835,7 +3820,6 @@ When you upgrade to 8.7.0, use the `/action_status` endpoint.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-147199]]
|
||||
.Removes the preconfiguration API route
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -4298,7 +4282,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.6.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-143081]]
|
||||
.Changes the `histogram:maxBars` default setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -4314,7 +4297,6 @@ For each {kibana-ref}/xpack-spaces.html[space], complete the following to change
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-158338]]
|
||||
.CSV reports use PIT instead of Scroll
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -4742,7 +4724,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.5.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-141757]]
|
||||
.Updates bulk action API to return actionId instead of agent success
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -4754,7 +4735,6 @@ When you use `FleetBulkResponse`, you now receive only `actionId` responses.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-139431]]
|
||||
.Removes filter validation for ad-hoc data views
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -4766,7 +4746,6 @@ Filters associated with unknown data views now display a warning message instead
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-138677]]
|
||||
.Removes the `package_policies` field from the agent policy saved object
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -5240,7 +5219,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.4.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-135669]]
|
||||
.xpack.agents.* are uneditable in UI when defined in kibana.yml
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -5254,7 +5232,6 @@ To configure `setxpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.agents.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-134336]]
|
||||
.Removes the legacy charts library
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -5831,7 +5808,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade, review the breaking change, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-129581]]
|
||||
.Removes Quandl and Graphite integrations
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -5845,7 +5821,6 @@ To leave your feedback about the removal of `.quandl` and `.graphite`, go to the
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-134855]]
|
||||
.Makes Osquery All with All base privilege
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -6822,7 +6797,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.1.0, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-121435]]
|
||||
.Removes legacy CSV export type
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -6834,7 +6808,6 @@ If you are using 7.13.0 and earlier, {kibana-ref-all}/8.1/automating-report-gene
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-121369]]
|
||||
.Removes legacy PDF shim
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7186,7 +7159,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade to 8.0.0, review the breaking change, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-123754]]
|
||||
.Removes the `console.ssl` setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7314,7 +7286,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade, review the breaking change, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-122722]]
|
||||
.Removes the ability to use `elasticsearch.username: elastic` in production
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7396,7 +7367,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
Before you upgrade, review the breaking changes, then mitigate the impact to your application.
|
||||
|
||||
[discrete]
|
||||
[[breaking-118854]]
|
||||
.Splits package policy `upgrade` endpoint for Fleet
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7432,7 +7402,6 @@ The endpoint is now split into two separate endpoints:
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-119945]]
|
||||
.Removes APM jobs from Machine Learning
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7444,7 +7413,6 @@ When you upgrade to 8.0.0, you are unable to create and view the APM Node.js and
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-118300]]
|
||||
.Fails migrations for unknown types
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7456,7 +7424,6 @@ To complete the migration, re enable plugins or delete documents from the index
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-116821]]
|
||||
.Removes deprecated config fields from Logs and Metrics APIs and saved objects
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7487,7 +7454,6 @@ To review the breaking changes in previous versions, refer to the following:
|
|||
Deprecated functionality does not have an immediate impact on your application, but we strongly recommend you make the necessary updates after you complete the upgrade.
|
||||
|
||||
[discrete]
|
||||
[[deprecation-120689]]
|
||||
.Renames the `autocreate` data view APM setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7499,7 +7465,6 @@ To automatically create data views in APM, use `xpack.apm.autoCreateApmDataView`
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[deprecation-119494]]
|
||||
.Updates Fleet API to improve consistency
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7696,7 +7661,6 @@ To review the breaking changes in previous versions, refer to the following:
|
|||
==== Alerting
|
||||
|
||||
[discrete]
|
||||
[[breaking-114558]]
|
||||
.Removes `xpack.task_manager.index`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7708,7 +7672,6 @@ Before you upgrade to 8.0.0, remove `xpack.task_manager.index` from kibana.yml.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113461]]
|
||||
.Removes ability to remove plugins
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7724,7 +7687,6 @@ Before you upgrade to 8.0.0, remove `xpack.actions.enabled` from kibana.yml.
|
|||
==== Lens & visualizations
|
||||
|
||||
[discrete]
|
||||
[[breaking-113516]]
|
||||
.Removes display options from legacy gauge
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7736,7 +7698,6 @@ When you create aggregation-based gauge visualizations, the *Display warnings* o
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-112643]]
|
||||
.Removes settings from visEditors plugins
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7781,7 +7742,6 @@ Before you upgrade, make the following changes in kibana.yml:
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-111704]]
|
||||
.Removes dimming opacity setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7793,7 +7753,6 @@ When you upgrade to 8.0.0, you are no longer able to configure the dimming opact
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-110985]]
|
||||
.Removes Less stylesheet support
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7805,7 +7764,6 @@ Existing less stylesheets are automatically converted to CSS stylesheets.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-110571]]
|
||||
.Disables the input string mode
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7827,7 +7785,6 @@ To use index patterns and {es} indices in *TSVB* visualizations:
|
|||
==== Logs
|
||||
|
||||
[discrete]
|
||||
[[breaking-115974]]
|
||||
.Removes deprecated alias config entries
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7839,7 +7796,6 @@ Before you upgrade, remove the settings from kibana.yml, then configure the sett
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-61302]]
|
||||
.Removes configurable fields in settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7855,7 +7811,6 @@ Configure the settings in https://www.elastic.co/guide/en/ecs/current/ecs-refere
|
|||
==== Machine learning
|
||||
|
||||
[discrete]
|
||||
[[breaking-115444]]
|
||||
.Grants access to machine learning features when base privileges are used
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7871,7 +7826,6 @@ If you do not want to grant users privileges to machine learning features, updat
|
|||
==== Maps
|
||||
|
||||
[discrete]
|
||||
[[breaking-116184]]
|
||||
.Removes proxyElasticMapsServiceInMaps
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7887,7 +7841,6 @@ Install the on-prem version of the <<maps-connect-to-ems,Elastic Maps Service>>,
|
|||
==== Operations
|
||||
|
||||
[discrete]
|
||||
[[breaking-111535]]
|
||||
.Removes environment variables
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7903,7 +7856,6 @@ Replace the `CONFIG_PATH` environment variable with `KBN_PATH_CONF`, and replace
|
|||
==== Platform
|
||||
|
||||
[discrete]
|
||||
[[breaking-114379]]
|
||||
.Removes supports for csp.rules configuration
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7915,7 +7867,6 @@ Configuring the default `csp.script_src`, `csp.workers_src`, and `csp.style_src`
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113653]]
|
||||
.Changes and removes deprecated core settings and deprecated settings from core plugins
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7949,7 +7900,6 @@ For more information, refer to {kibana-pull}113653[#113653].
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113495]]
|
||||
.Removes `enabled` settings from plugins
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7966,7 +7916,6 @@ Before you upgrade to 8.0.0:
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113367]]
|
||||
.Removes `--plugin-dir` cli option
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -7978,7 +7927,6 @@ Before you upgrade to 8.0.0, remove `plugins.scanDirs` from kibana.yml.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113296]]
|
||||
.Removes support for `optimize.*` settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8012,7 +7960,6 @@ To run the `@kbn/optimizer` separately in development, pass `--no-optimizer` to
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113173]]
|
||||
.Removes `so/server/es` settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8031,7 +7978,6 @@ Before you upgrade to 8.0.0., remove these settings from kibana.yml.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-113068]]
|
||||
.Adds requirement for inline scripting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8043,7 +7989,6 @@ Enable {ref}/modules-scripting-security.html[inline scripting].
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-112773]]
|
||||
.Removes `kibana.index` settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8055,7 +8000,6 @@ Use spaces, cross-cluster replication, or cross-cluster search. To migrate to <<
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-112305]]
|
||||
.Removes legacy logging
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8071,7 +8015,6 @@ Use the new <<logging-configuration,logging system configuration>>.
|
|||
==== Reporting
|
||||
|
||||
[discrete]
|
||||
[[breaking-114216]]
|
||||
.Removes reporting settings
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8097,7 +8040,6 @@ Before you upgrade to 8.0.0, remove the settings from kibana.yml.
|
|||
==== REST API
|
||||
|
||||
[discrete]
|
||||
[[breaking-114730]]
|
||||
.Removes `/api/settings`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8113,7 +8055,6 @@ Use `/api/stats`.
|
|||
==== Security
|
||||
|
||||
[discrete]
|
||||
[[breaking-116191]]
|
||||
.Removes legacy audit logger
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8200,7 +8141,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
To review the breaking changes in the previous version, refer to <<breaking-changes-8.0.0-alpha1,8.0.0-alpha1>>.
|
||||
|
||||
[discrete]
|
||||
[[breaking-110830]]
|
||||
.Changes the `GET /api/status` default behavior
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8212,7 +8152,6 @@ To retrieve the {kib} status in the previous format, use `GET /api/status?v7form
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-110738]]
|
||||
.Removes support for legacy exports
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8224,7 +8163,6 @@ Using the user interface to import saved objects is restricted to `.ndjson` form
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-109896]]
|
||||
.Removes `map.regionmap.*`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8242,7 +8180,6 @@ If you have maps that use `map.regionmap` layers:
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-109798]]
|
||||
.Removes `kibana.defaultAppId`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8254,7 +8191,6 @@ When you upgrade, remove `kibana.defaultAppId` from your kibana.yml file. To con
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-109350]]
|
||||
.Removes `courier:batchSearches`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8266,7 +8202,6 @@ When you upgrade, the `courier:batchSearches` setting will no longer be availabl
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-108111]]
|
||||
.Removes `xpack.task_manager.index`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8278,7 +8213,6 @@ When you upgrade, remove `xpack.task_manager.index` from your kibana.yml file.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-108103]]
|
||||
.Removes dashboard-only mode
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8290,7 +8224,6 @@ To grant users access to only dashboards, create a new role, then assign only th
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-105979]]
|
||||
.Removes `xpack.maps.showMapVisualizationTypes`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8343,7 +8276,6 @@ Breaking changes can prevent your application from optimal operation and perform
|
|||
==== Enterprise Search changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-106307]]
|
||||
.Required security plugin in 8.0
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8359,7 +8291,6 @@ Enable X-Pack Security.
|
|||
==== Index pattern changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-35173]]
|
||||
.Removed support for time-based interval index patterns
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8375,7 +8306,6 @@ You must migrate your time_based index patterns to a wildcard pattern. For examp
|
|||
==== Operations changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-93835]]
|
||||
.Removed platform from archive root directory
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8387,7 +8317,6 @@ To use the new folder, update the configuration management tools and automation.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-90511]]
|
||||
.Removed default support for TLS v1.0 and v1.1
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8399,7 +8328,6 @@ To enable support, set `--tls-min-1.0` in the `node.options` configuration file.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-74424]]
|
||||
.Removed support for sysv init
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8411,7 +8339,6 @@ If your installation uses .deb or .rpm packages with SysV, migrate to systemd.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-42353]]
|
||||
.Disabled response logging as a default
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8447,7 +8374,6 @@ logging:
|
|||
==== Reporting changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-52539]]
|
||||
.Legacy job parameters are no longer supported
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8463,7 +8389,6 @@ If you use POST URL snippets to automatically generate PDF reports, regenerate t
|
|||
==== Security changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-47929]]
|
||||
.Removed `/api/security/v1/saml` route
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8475,7 +8400,6 @@ Use the `/api/security/saml/callback` route, or wait to upgrade to 8.0.0-alpha2
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-41700]]
|
||||
.Reject legacy browsers by default
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8491,7 +8415,6 @@ To enable support for legacy browsers, set `csp.strict: false` in kibana.yml. To
|
|||
==== Settings changes
|
||||
|
||||
[discrete]
|
||||
[[breaking-106061]]
|
||||
.Use new session timeout defaults
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8506,7 +8429,6 @@ Use the following default values:
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-87114]]
|
||||
.Removed support for setting `server.host` to '0'
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8518,7 +8440,6 @@ You are now unable to use `0` as the `server.host`.
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-38657]]
|
||||
.Removed `xpack.security.public` and `xpack.security.authProviders`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8530,7 +8451,6 @@ Use the `xpack.security.authc.saml.realm` and `xpack.security.authc.providers` s
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-22696]]
|
||||
.Removed useUTC deprecation
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8542,7 +8462,6 @@ The default timezone is UTC. To change the timezone, set `logging.timezone: fals
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[breaking-32049]]
|
||||
.Removed environment variables `CONFIG_PATH` and `DATA_PATH`
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8560,7 +8479,6 @@ Use the environment variable `KBN_PATH_CONF` instead of `CONFIG_PATH`. Use the
|
|||
The following functionality is deprecated in 8.0.0, and will be removed in 9.0.0. Deprecated functionality does not have an immediate impact on your application, but we strongly recommend you make the necessary updates after you complete the upgrade.
|
||||
|
||||
[discrete]
|
||||
[[deprecation-74424]]
|
||||
.Removed support for SysV init
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
@ -8572,7 +8490,6 @@ If your system doesn't have `service` aliased to use kibana.service, use `system
|
|||
====
|
||||
|
||||
[discrete]
|
||||
[[deprecation-33603]]
|
||||
.Removed `xpack:defaultAdminEmail` setting
|
||||
[%collapsible]
|
||||
====
|
||||
|
|
|
|||
|
|
@ -6,6 +6,8 @@ To upgrade from 7.16.0 or earlier to {version},
|
|||
{stack-ref}/upgrading-elastic-stack.html#prepare-to-upgrade[prepare for the upgrade].
|
||||
Before you upgrade, you must resolve all critical issues identified by the *Upgrade Assistant*.
|
||||
|
||||
In addition, we recommend to carefully review the <<breaking-changes-summary,list of breaking changes and deprecations>> and to take any necessary actions to mitigate their impact on the upgrade.
|
||||
|
||||
Rolling upgrades are unsupported in {kib}. To upgrade,
|
||||
you must shut down all {kib} instances, install the new software, and restart {kib}.
|
||||
Upgrading while older {kib} instances are running can cause data loss or upgrade failures.
|
||||
|
|
|
|||
1716
docs/upgrade-notes.asciidoc
Normal file
1716
docs/upgrade-notes.asciidoc
Normal file
File diff suppressed because it is too large
Load diff
Loading…
Add table
Add a link
Reference in a new issue