[DOCS] Adds 7.16.0 release notes

[KOTungseth]

Summary

Adds the release notes for the 7.16.0 release.

Preview

https://kibana_119856.docs-preview.app.elstc.co/guide/en/kibana/7.16/release-notes-7.16.0.html

[elasticmachine]

Pinging @elastic/kibana-docs (Team:Docs)

[gtback]

@elasticmachine run elasticsearch-ci/docs

[melissaburpo]

Hi @KOTungseth, if it's not too late, I'd like to add a note about Osquery to the breaking changes section for 7.16. I've drafted it below, but please feel free to update this as needed.

[discrete]
[[breaking-107345]]
.Replaces Osquery Scheduled Query Groups with Packs
[%collapsible]
====
*Details* +
Queries are now scheduled using Packs. 
For more information, refer to {kibana-pull}107345[#107345].
*Impact* +
When you upgrade to 7.16.0, any existing Scheduled Query Groups are converted to Packs. 
Queries in the updated Packs are scheduled for the same agent policy as the original 
Scheduled Query Group. Action IDs for scheduled queries in a pack have the 
format `pack_<pack_name>_<query ID>`. 
====

[jportner]

Sorry for the late review on this!

[cjcenizal]

@KOTungseth I'm seeing a missing deprecation notice for the removal of console.proxyFilter and console.proxyConfig Kibana settings (#113555). There's a release note on that PR. Could we please add that to these release notes? Thanks!

[LeeDr]

I'm thinking we should add something else about the Upgrade Assistant and/or upgrade plans.

The only place I see mentioning the Upgrade Assistant is;
Upgrade Assistant now displays the progress of your reindexing tasks {kibana-pull}114275[#114275]

Which glosses right over the fact that the Upgrade Assistant was added in this release.

People who do find the UA, could be easily led to believe that once the critical deprecations are resolved that they can upgrade to 8.0. But they generally shouldn't try that unless it's a test system they don't care about. They can address any deprecations they see in the UA, but they should upgrade to 7.17 and use the UA again before upgrading to 8.0.
One item in particular that is not in the 7.16 UA is the system indices migration.
/cc @cjcenizal

.. Maybe we just make it clear in the 8.0 release notes that users who are upgrading should upgrade to 7.17 first.

[cjcenizal]

@LeeDr Great point. I agree. For these release notes let's add something like this:

Upgrade Assistant

A preview release of Upgrade Assistant is available in 7.16. You can use this version of Upgrade Assistant to address deprecations in your data. We expect to add additional features in subsequent 7.x releases, which will help you prepare for your 8.0 upgrade.

[lcawl]

ML PRs LGTM

[KOTungseth]

Upgrade Assistant now displays the progress of your reindexing tasks

@LeeDr @cjcenizal each item in the release notes is tied to a PR. Is there a PR I can reference for the UA work?

For future releases, if you add the release_note:feature label, the PR will automatically be added to the Features section.

[cjcenizal]

@KOTungseth Unfortunately, the Upgrade Assistant work was such a large change that it would be impractical to link to a representative set of PRs. We could link to all Upgrade Assistant PRs, which will help folks discover the work that went into this feature. I expect that as the Stack Management team works on larger projects we'll find ourselves in this situation more often.

FWIW I deliberately excluded the bit about reindexing from the [release note I suggested]
(#119856 (comment)), because the scope of changes extended far beyond it.

[cjcenizal]

It just occurred to me that we plan to write a blog post on Upgrade Assistant. Would it be worth linking to this post from the release notes?

[gchaps]

The Upgrade Assistant is also mentioned in the What's New. I think that might be the better place to link to the blog.

[dedemorton]

Adding a few more comments for things that I noticed when I was working on the Fleet/Agent release notes.

[dedemorton]

Again here. @EamonnTP or @bmorelli25 should review. Some of this info just doesn't seem useful to end users, IMO.

[dedemorton]

I'm on the fence about whether to include this one because I think it falls into the category of things users will see when they interact with the UI. If we keep it, I think we need to be more descriptive and say something like:

Adds prompt for users to add an agent if they add an integration to an agent policy with no agents

That's a mouthful, though. WDYT?

[KOTungseth]

Better than what's there! Updated.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f5c7cc0

History

• 💚 Build #11516 succeeded 0e05952
• 💚 Build #11409 succeeded 7f6c082
• 💚 Build #11408 succeeded f4d1ceb
• 💚 Build #10982 succeeded 48caf9c
• 💚 Build #10847 succeeded c1a6c0a
• 💚 Build #10489 succeeded 4cd8a21

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @KOTungseth

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 24d9ee4

History

• 💚 Build #11529 succeeded f9e2dd6
• 💚 Build #11528 succeeded d1021cf
• 💚 Build #11527 succeeded 17555e4
• 💚 Build #11522 succeeded c9c01a1
• 💚 Build #11520 succeeded 92a9228
• 💚 Build #11516 succeeded 0e05952

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @KOTungseth