Kibana 8.0.0
editKibana 8.0.0
editReview the Kibana 8.0.0 changes, then use the Upgrade Assistant to complete the upgrade.
Breaking change
editBreaking changes can prevent your application from optimal operation and performance. Before you upgrade to 8.0.0, review the breaking change, then mitigate the impact to your application.
Removes the console.ssl setting
Details
The console.ssl setting has been removed. For more information, refer to #123754.
Impact
Before you upgrade to 8.0.0, remove console.ssl from kibana.yml.
To review the breaking changes in previous versions, refer to the following:
8.0.0-rc2 | 8.0.0-rc1 | 8.0.0-beta1 | 8.0.0-alpha2 | 8.0.0-alpha1
Deprecation
editThe 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 upgrade to 8.0.0.
Removes support for monitoring.cluster_alerts.allowedSpaces
Details
The monitoring.cluster_alerts.allowedSpaces setting, which Kibana uses to create Stack Monitoring alerts, has been removed. For more information, refer to #123229.
Impact
Before you upgrade to 8.0.0, remove monitoring.cluster_alerts.allowedSpaces from kibana.yml.
To review the deprecations in previous versions, refer to the following:
Known issue
editImporting and copying saved objects causes weak links to break
Details
Kibana supports weak links in some saved objects. For example, a dashboard may include a Markdown panel that contains a relative URL to
another dashboard. Weak links are defined by free text, not the saved object’s relationships, and can break if both of the following
conditions are true:
- You are importing saved objects into multiple spaces, OR you are copying saved objects into another space
- Before you upgraded to 8.0.0, the saved objects did not already exist in the destinations
In 8.0.0 and later, weak links break because saved object IDs can change during import or copy. This applies to both the UI and the API. This issue will be fixed 8.0.1 and 8.1.0. For more information, refer to #123550.
Impact
Saved objects in 7.x that are migrated during upgrade are not impacted.
Only new saved objects that are imported or copied multiple times (causing object IDs to change) are impacted.
If you are impacted, you can re-import or re-copy your saved objects after the fix is
implemented to preserve the weak links.
Features
editFor information about the features introduced in 8.0.0, refer to What’s new in 8.0.
- Elastic Security
- For the Elastic Security 8.0.0 release information, refer to Elastic Security Solution Release Notes.
To review the features in previous versions, refer to the following: