431 lines
14 KiB
Plaintext
431 lines
14 KiB
Plaintext
[[release-notes]]
|
||
= Release notes
|
||
|
||
[partintro]
|
||
--
|
||
// Use these for links to issue and pulls. Note issues and pulls redirect one to
|
||
// each other on Github, so don't worry too much on using the right prefix.
|
||
:issue: https://github.com/elastic/kibana/issues/
|
||
:pull: https://github.com/elastic/kibana/pull/
|
||
|
||
Review important information about the {kib} 8.0.0 releases.
|
||
|
||
* <<release-notes-8.0.0-alpha2>>
|
||
* <<release-notes-8.0.0-alpha1>>
|
||
|
||
--
|
||
|
||
[[release-notes-8.0.0-alpha2]]
|
||
== {kib} 8.0.0-alpha2
|
||
|
||
Review the {kib} 8.0.0-alpha2 changes, then use the <<upgrade-assistant,Upgrade Assistant>> to complete the upgrade.
|
||
|
||
[float]
|
||
[[breaking-changes-8.0.0-alpha2]]
|
||
=== Breaking changes
|
||
|
||
Breaking changes can prevent your application from optimal operation and performance. Review the following breaking changes, then mitigate the impact to your application.
|
||
|
||
//tag::notable-breaking-changes[]
|
||
|
||
[discrete]
|
||
[[breaking-110830]]
|
||
.Changes the `GET /api/status` default behavior
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
`GET /api/status` reports a new and more verbose payload. For more information, refer to {kibana-pull}110830[#110830].
|
||
|
||
*Impact* +
|
||
To retrieve the {kib} status in the previous format, use `GET /api/status?v7format=true`.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-110738]]
|
||
.Removes support for legacy exports
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
In {kib} 8.0.0 and later, the legacy format from {kib} 6.x is unsupported. For more information, refer to {kibana-pull}110738[#110738]
|
||
|
||
*Impact* +
|
||
Using the user interface to import saved objects is restricted to `.ndjson` format imports.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-109896]]
|
||
.Removes `map.regionmap.*`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The deprecated `map.regionmap.*` setting in kibana.yml has been removed. For more information, refer to {kibana-pull}109896[#109896].
|
||
|
||
*Impact* +
|
||
If you have maps that use `map.regionmap` layers:
|
||
|
||
. Remove the `map.regionmap` layer.
|
||
|
||
. To recreate the choropleth layer, use <<import-geospatial-data,GeoJSON upload>> to index your static vector data into {es}.
|
||
|
||
. Create a choropleth layer from the indexed vector data.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-109798]]
|
||
.Removes `kibana.defaultAppId`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The deprecated `kibana.defaultAppId` setting in kibana.yml, which is also available as `kibana_legacy.defaultAppId`, has been removed. For more information, refer to {kibana-pull}109798[#109798].
|
||
|
||
*Impact* +
|
||
When you upgrade, remove `kibana.defaultAppId` from your kibana.yml file. To configure the default route for users when they enter a space, use the <<defaultroute,`defaultRoute`>> in *Advanced Settings*.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-109350]]
|
||
.Removes `courier:batchSearches`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The deprecated `courier:batchSearches` setting in *Advanced Settings* has been removed. For more information, refer to {kibana-pull}109350[#109350].
|
||
|
||
*Impact* +
|
||
When you upgrade, the `courier:batchSearches` setting will no longer be available.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-108111]]
|
||
.Removes `xpack.task_manager.index`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The deprecated `xpack.task_manager.index` setting in kibana.yml has been removed. For more information, refer to {kibana-pull}108111[#108111].
|
||
|
||
*Impact* +
|
||
When you upgrade, remove `xpack.task_manager.index` from your kibana.yml file.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-108103]]
|
||
.Removes dashboard-only mode
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The legacy dashboard-only mode has been removed. For more information, refer to {kibana-pull}108103[#108103].
|
||
|
||
*Impact* +
|
||
To grant users access to only dashboards, create a new role, then assign only the *Dashboard* feature privilege. For more information, refer to <<kibana-feature-privileges,{kib} privileges>>.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-105979]]
|
||
.Removes `xpack.maps.showMapVisualizationTypes`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The deprecated `xpack.maps.showMapVisualizationTypes` setting in kibana.yml has been removed. For more information, refer to {kibana-pull}105979[#105979]
|
||
|
||
*Impact* +
|
||
When you upgrade, remove `xpack.maps.showMapVisualizationTypes` from your kibana.yml file.
|
||
====
|
||
|
||
For the {kib} 8.0.0-alpha1 breaking changes, refer to <<breaking-changes-8.0.0,Breaking changes>>.
|
||
|
||
//end::notable-breaking-changes[]
|
||
|
||
[float]
|
||
[[features-8.0.0-alpha2]]
|
||
=== Features
|
||
The 8.0.0-alpha2 release adds the following new and notable feature.
|
||
|
||
Security::
|
||
* Adds the interactive setup mode {kibana-pull}106881[#106881]
|
||
|
||
[float]
|
||
[[enhancement-v8.0.0-alpha2]]
|
||
=== Enhancements
|
||
The 8.0.0-alpha2 release includes the following enhancements.
|
||
|
||
Elastic Security::
|
||
For the Elastic Security 8.0.0-alpha2 release information, refer to {security-guide}/release-notes.html[_Elastic Security Solution Release Notes_].
|
||
Security::
|
||
* Interactive setup mode {kibana-pull}106881[#106881]
|
||
|
||
[float]
|
||
[[fixes-v8.0.0-alpha2]]
|
||
=== Bug fix
|
||
The 8.0.0-alpha2 release includes the following bug fix.
|
||
|
||
Operations::
|
||
* Moves systemd service to /usr/lib/systemd/system {kibana-pull}83571[#83571]
|
||
|
||
[[release-notes-8.0.0-alpha1]]
|
||
== {kib} 8.0.0-alpha1
|
||
|
||
Review the {kib} 8.0.0-alpha1 changes, then use the <<upgrade-assistant,Upgrade Assistant>> to complete the upgrade.
|
||
|
||
[float]
|
||
[[breaking-changes-8.0.0]]
|
||
=== Breaking changes
|
||
|
||
Breaking changes can prevent your application from optimal operation and performance. Review the breaking changes, then mitigate the impact to your application.
|
||
|
||
//tag::notable-breaking-changes[]
|
||
|
||
[float]
|
||
[[enterprise-search-change]]
|
||
==== Enterprise Search changes
|
||
|
||
[discrete]
|
||
[[breaking-106307]]
|
||
.Required security plugin in 8.0
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
Enterprise Search now requires that you enable X-Pack Security. For more information, refer to {kibana-pull}106307[#106307]
|
||
|
||
*Impact* +
|
||
Enable X-Pack Security.
|
||
====
|
||
|
||
[float]
|
||
[[index-pattern-change]]
|
||
==== Index pattern changes
|
||
|
||
[discrete]
|
||
[[breaking-35173]]
|
||
.Removed support for time-based interval index patterns
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
Time-based interval index patterns were deprecated in 5.x. In 6.x, you could no longer create time-based interval index patterns, but they continued to function as expected. Support for these index patterns has been removed in 8.0. For more information, refer to {kibana-pull}35173[#35173]
|
||
|
||
*Impact* +
|
||
You must migrate your time_based index patterns to a wildcard pattern. For example, logstash-*.
|
||
====
|
||
|
||
[float]
|
||
[[operations-changes]]
|
||
==== Operations changes
|
||
|
||
[discrete]
|
||
[[breaking-93835]]
|
||
.Removed platform from archive root directory
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
After you extract an archive, the output directory no longer includes the target platform. For example, `kibana-8.0.0-linux-aarch64.tar.gz` produces a `kibana-8.0.0` folder. For more information, refer to {kibana-pull}93835[#93835].
|
||
|
||
*Impact* +
|
||
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]
|
||
====
|
||
*Details* +
|
||
The default support for TLS v1.0 and v1.1 has been removed. For more information, refer to {kibana-pull}90511[#90511].
|
||
|
||
*Impact* +
|
||
To enable support, set `--tls-min-1.0` in the `node.options` configuration file. To locate the configuration file, go to the kibana/config folder or any other configuration with the `KBN_PATH_CONF` environment variable. For example, if you are using a Debian-based system, the configuration file is located in /etc/kibana.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-74424]]
|
||
.Removed support for sysv init
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
All supported operating systems use systemd service files. Any system that doesn’t have `service` aliased to use kibana.service should use `systemctl start kibana.service` instead of `service start kibana`. For more information, refer to {kibana-pull}74424[#74424].
|
||
|
||
*Impact* +
|
||
If your installation uses .deb or .rpm packages with SysV, migrate to systemd.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-42353]]
|
||
.Disabled response logging as a default
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
In previous versions, all events are logged in `json` when `logging.json:true`. With the new logging configuration, you can choose the `json` and pattern output formats with layouts. For more information, refer to {kibana-pull}42353[#42353].
|
||
|
||
*Impact* +
|
||
To restore the previous behavior, configure the logging format for each custom appender with the `appender.layout property` in kibana.yml. There is no default for custom appenders, and each appender must be configured expilictly.
|
||
|
||
[source,yaml]
|
||
-------------------
|
||
logging:
|
||
appenders:
|
||
custom_console:
|
||
type: console
|
||
layout:
|
||
type: pattern
|
||
custom_json:
|
||
type: console
|
||
layout:
|
||
type: json
|
||
loggers:
|
||
- name: plugins.myPlugin
|
||
appenders: [custom_console]
|
||
root:
|
||
appenders: [default, custom_json]
|
||
level: warn
|
||
-------------------
|
||
====
|
||
|
||
[float]
|
||
[[reporting-changes-8.0.0-alpha1]]
|
||
==== Reporting changes
|
||
|
||
[discrete]
|
||
[[breaking-52539]]
|
||
.Legacy job parameters are no longer supported
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
*Reporting* is no longer compatible with POST URL snippets generated with {kib} 6.2.0 and earlier. For more information, refer to {kibana-pull}52539[#52539]
|
||
|
||
*Impact* +
|
||
If you use POST URL snippets to automatically generate PDF reports, regenerate the POST URL strings.
|
||
====
|
||
|
||
[float]
|
||
[[rest-api-changes]]
|
||
==== Security changes
|
||
|
||
[discrete]
|
||
[[breaking-47929]]
|
||
.Removed `/api/security/v1/saml` route
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The `/api/security/v1/saml` route has been removed and is reflected in the kibana.yml `server.xsrf.whitelist` setting, {es}, and the Identity Provider SAML settings. For more information, refer to {kibana-pull}47929[#47929]
|
||
|
||
*Impact* +
|
||
Use the `/api/security/saml/callback` route, or wait to upgrade to 8.0.0-alpha2 when the `/api/security/saml/callback` route breaking change is reverted.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-41700]]
|
||
.Reject legacy browsers by default
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
To provide the maximum level of protection for most installations, the csp.strict config is now enabled by default. Legacy browsers not supported by Kibana, such as Internet Explorer 11, are unable to access {kib} unless explicitly enabled. All browsers officially supported by Kibana do not have this issue. For more information, refer to {kibana-pull}41700[#41700]
|
||
|
||
*Impact* +
|
||
To enable support for legacy browsers, set `csp.strict: false` in kibana.yml. To effectively enforce the security protocol, we strongly discourage disabling `csp.strict` unless it is critical that you support Internet Explorer 11.
|
||
====
|
||
|
||
[float]
|
||
[[settings-changes-8.0.0-alpha1]]
|
||
==== Settings changes
|
||
|
||
[discrete]
|
||
[[breaking-106061]]
|
||
.Use new session timeout defaults
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The default values for the session timeout `xpack.security.session.{lifespan|idleTimeout}` settings have changed. For more information, refer to {kibana-pull}106061[#106061]
|
||
|
||
*Impact* +
|
||
Use the following default values:
|
||
|
||
* `xpack.security.session.idleTimeout: 1h`
|
||
* `xpack.security.session.lifespan: 30d`
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-87114]]
|
||
.Removed support for setting `server.host` to '0'
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
Support for configuring {kib} with `0` as the `server.host` has been removed. Please use `0.0.0.0` instead. For more information, refer to {kibana-pull}87114[#87114]
|
||
|
||
*Impact* +
|
||
You are now unable to use `0` as the `server.host`.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-38657]]
|
||
.Removed `xpack.security.public` and `xpack.security.authProviders`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The `xpack.security.public` and `xpack.security.authProviders` settings have been removed. For more information, refer to {kibana-pull}38657[#38657]
|
||
|
||
*Impact* +
|
||
Use the `xpack.security.authc.saml.realm` and `xpack.security.authc.providers` settings.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-22696]]
|
||
.Removed useUTC deprecation
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The `logging.useUTC` setting has been removed. For more information, refer to {kibana-pull}22696[#22696]
|
||
|
||
*Impact* +
|
||
The default timezone is UTC. To change the timezone, set `logging.timezone: false` in kibana.yml. Change the timezone when the system, such as a docker container, is configured for a nonlocal timezone.
|
||
====
|
||
|
||
[discrete]
|
||
[[breaking-32049]]
|
||
.Removed environment variables `CONFIG_PATH` and `DATA_PATH`
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The environment variables `CONFIG_PATH` and `DATA_PATH` have been removed. For more information, refer to {kibana-pull}32049[#32049]
|
||
|
||
*Impact* +
|
||
Use the environment variable `KBN_PATH_CONF` instead of `CONFIG_PATH`. Use the setting `path.data` instead of `DATA_PATH`.
|
||
====
|
||
|
||
// end::notable-breaking-changes[]
|
||
|
||
[float]
|
||
[[deprecations-8.0.0]]
|
||
=== Deprecations
|
||
|
||
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]
|
||
====
|
||
*Details* +
|
||
Systems that don't have `service` aliased to use kibana.service are unable to use `service start kibana`. For more information, refer to {kibana-pull}74424[#74424]
|
||
|
||
*Impact* +
|
||
If your system doesn't have `service` aliased to use kibana.service, use `systemctl start kibana.service`.
|
||
====
|
||
|
||
[discrete]
|
||
[[deprecation-33603]]
|
||
.Removed `xpack:defaultAdminEmail` setting
|
||
[%collapsible]
|
||
====
|
||
*Details* +
|
||
The `xpack:default_admin_email` setting for monitoring use has been removed. For more information, refer to {kibana-pull}33603[#33603]
|
||
|
||
*Impact* +
|
||
Use the `xpack.monitoring.clusterAlertsEmail` in kibana.yml.
|
||
====
|
||
|
||
[float]
|
||
[[enhancements-and-bug-fixes-v8.0.0]]
|
||
=== Bug fix
|
||
|
||
The 8.0.0-alpha1 release includes the following bug fix.
|
||
|
||
Operations::
|
||
* Moves systemd service to /usr/lib/systemd/system {kibana-pull}83571[#83571]
|