8db71f1feb
This PR adds 9.0 GA release notes for Kibana. - [x] convert the [9.0.0rc1 release notes](https://github.com/elastic/stack-docs/blob/9.0/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc) into markdown to prepare for the release to the new docs site - [x] Add anchors `$$$kibana-PR$$$` to breaking changes for links from Upgrade Assistant. cc @lcawl FYI - [x] Run release notes tool for post-rc1 changes - [x] Reviews ## For reviewers Preview link: https://docs-v3-preview.elastic.dev/elastic/kibana/pull/215772/release-notes/ Release notes are adopting a new structure from 9.0, identical across all Elastic products. Pages are broken down as follows: - A main page listing all new features, enhancements, and bug fixes. Each new release gets added to the same page. (9.1 will be above 9.0, etc.) - Subpages for breaking changes, deprecations, and known issues. - There is no longer a "What's new page". This is replaced with a link to the blog's release announcement from this page, that will be the "home page" for release notes in the new assembled docs website: https://staging-website.elastic.co/docs/release-notes/ (not visible in this PR) --------- Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co>
1.9 KiB
| navigation_title |
|---|
| Known issues |
Kibana known issues
9.0.0
::::{dropdown} Issue with follower indices during upgrade :name: ua-follower-indices
Details
In Upgrade Assistant, follower indices may be identified to be reindexed. However, this is not a valid migration path and will result in an error. Instead, the recommendation is to mark as read-only and unfollow the leader index. Cross-cluster replication on that index will not be possible.
Find additional information in the upgrade documentation.
::::
::::{dropdown} Unexpected deprecation warnings for APM indices during upgrade :name: known-issue-apm-upgrade-on-ech
Details
When upgrading an {{ech}} deployment to {{stack}} 9.0.0, you may see deprecation warnings for APM indices, even if you are not using APM.
If your deployment ever ran on {{stack}} 7.x, these APM indices have been created automatically at that time, even if you didn't use APM. In this case, these indices exist and are empty.
Action
To proceed with the upgrade to 9.0.0, you must resolve all deprecation notices for indices beginning with the name apm-7 by selecting Mark as read-only for each of them.
::::
::::{dropdown} Upgrade Assistant - Rollup jobs need to be stopped before rollup indices are reindexed :name: known-issue-211850
Details
Rollup indices, like all indices, created in 7.x or earlier need to be reindexed in preparation for migration to 9.0. However, in addition to the normal reindex process the rollup job also needs to be accounted for.
Action
Stop the rollup job before reindexing begins otherwise there may be a gap in rollup data. You can restart the job can after reindexing is complete.
This needs to be performed manually until addressed in the upgrade assistant code.
View #211850.
::::