Add known issue for Kibana OOM crashes (#1672) (#1682)

(cherry picked from commit 6aa8a4f)

Co-authored-by: David Kilfoyle <[email protected]>

Author: mergify[bot]

docs/en/ingest-management/release-notes/release-notes-8.17.asciidoc

@@ -72,9 +72,26 @@ impact to your application.
 {agent}::
 * {agent} Docker images for {ecloud} have been reverted from having been based off of Ubuntu 24.04 to being based off of Ubuntu 20.04. This is to ensure compatibility with {ece}, support for new Wolfi-based images, and for GNU C Library (glibc) compatibility. {agent-pull}6393[#6393]
 
-//*Impact* +
-//<Describe how users should mitigate the change.> For more information, refer to {fleet-guide}/fleet-server.html[Fleet Server].
-//====
+[discrete]
+[[known-issues-8.17.1]]
+=== Known issues
+
+[[known-issue-1671]]
+.{kib} out of memory crashes on 1 GB {ecloud} {kib} instances using {elastic-sec} view
+[%collapsible]
+====
+
+*Details*
+
+{ecloud} deployments that use the smallest available {kib} instance size of 1 GB may crash due to out of memory errors when the Security UI is loaded. 
+
+*Impact* +
+
+The root cause is inefficient memory allocation, and this is exacerbated when the prebuilt security rules package is installed on the initial load of the {elastic-sec} UI.
+
+As a workaround, you can upgrade your deployment to 8.17.1 in which this issue has been resolved by https://github.com/elastic/kibana/pull/208869[#208869] and https://github.com/elastic/kibana/pull/208475[#208475].
+
+====
 
 [discrete]
 [[new-features-8.17.1]]