Add KVv2 known issue to release notes (#24632)

* Add KVv2 known issue to release notes

* Update website/content/partials/known-issues/kv2-url-change.mdx

* Update website/content/partials/known-issues/kv2-url-change.mdx

---------

Co-authored-by: Yoko Hyakuna <[email protected]>

Author: schavis

website/content/docs/release-notes/1.15.0.mdx

@@ -22,6 +22,7 @@ Version | Issue
 1.15.0 - 1.15.1 | [Vault storing references to ephemeral sub-loggers leading to unbounded memory consumption](/vault/docs/upgrading/upgrade-to-1.15.x#vault-is-storing-references-to-ephemeral-sub-loggers-leading-to-unbounded-memory-consumption)
 1.15.0 - 1.15.1 | [Internal error when vault policy in namespace does not exist](/vault/docs/upgrading/upgrade-to-1.15.x#internal-error-when-vault-policy-in-namespace-does-not-exist)
 1.15.0+ | [Sublogger levels not adjusted on reload](/vault/docs/upgrading/upgrade-to-1.15.x#sublogger-levels-unchanged-on-reload)
+1.15.0+ | [URL change for KV v2 plugin](/vault/docs/upgrading/upgrade-to-1.15.x#kv2-url-change)
 1.15.1  | [Fatal error during expiration metrics gathering causing Vault crash](/vault/docs/upgrading/upgrade-to-1.15.x#fatal-error-during-expiration-metrics-gathering-causing-vault-crash)
 
 

website/content/docs/upgrading/upgrade-to-1.15.x.mdx

@@ -63,4 +63,6 @@ option.
 
 @include 'known-issues/sublogger-levels-unchanged-on-reload.mdx'
 
+@include 'known-issues/kv2-url-change.mdx'
+
 @include 'known-issues/expiration-metrics-fatal-error.mdx'

website/content/partials/known-issues/kv2-url-change.mdx

@@ -0,0 +1,24 @@
+### URL change for KV v2 secrets engine ((#kv2-url-change))
+
+#### Affected versions
+
+1.15.0+
+
+#### Issue
+
+Recent improvements to the Vault UI updated the URL structure of the KV v2 secrets engine that affect existing URLs.
+
+Previously, URLs for KV v2 used the pattern:
+`ui/vault/secrets/hma/show/${secretPath}`. With the recent refactor, KV v2 URLs
+now use the following pattern:
+`ui/vault/secrets/hma/kv/${encodedUriComponent(secretPath)}/details`.
+
+Opening older URLs now result in 404 errors.
+
+#### Workaround
+
+Currently, no workaround exists.
+
+Improvements that include automatic redirects for older URLs are planned for
+1.15.4.
+