From 6bf505c1a3d9bcd375370b99bb98f0243e39541f Mon Sep 17 00:00:00 2001 From: Theron Voran Date: Fri, 28 Feb 2025 13:15:25 -0800 Subject: [PATCH] docs/events: update note about client redirect for 1.19 (#29705) * docs/events: update note about client redirect for 1.19 * Update website/content/docs/concepts/events.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- website/content/docs/concepts/events.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/concepts/events.mdx b/website/content/docs/concepts/events.mdx index 6506a6bdb6..3bb6e8ff0c 100644 --- a/website/content/docs/concepts/events.mdx +++ b/website/content/docs/concepts/events.mdx @@ -139,8 +139,8 @@ Here is an example event notification in JSON format: -For multi-node Vault deployments, Vault only accepts subscriptions on the active node. If a client attempts to subscribe to events on a standby node, -Vault will respond with a redirect to the active node. Vault uses the [`api_addr`](/vault/docs/configuration#api_addr) of the active node's configuration to route the redirect. +For multi-node Vault deployments, Vault only accepts subscriptions on the active node and performance standbys. +Vault reroutes subscription requests made to [non-performance standby nodes](/vault/docs/enterprise/performance-standby#disabling-performance-standbys) to the active node based on the [`api_addr`](/vault/docs/configuration#api_addr) configuration setting on the active node. Vault deployments with performance replication must subscribe to events on the primary performance cluster. Vault ignores subscriptions made from secondary