From c9e17d62193388e05c818c28ba4fabe57463229a Mon Sep 17 00:00:00 2001 From: Vishal Nayak Date: Mon, 11 Jul 2022 17:37:44 -0400 Subject: [PATCH] Document autopilot config differences at a high level (#15000) Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> --- .../docs/concepts/integrated-storage/autopilot.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/website/content/docs/concepts/integrated-storage/autopilot.mdx b/website/content/docs/concepts/integrated-storage/autopilot.mdx index 89c945f26..48c646f2e 100644 --- a/website/content/docs/concepts/integrated-storage/autopilot.mdx +++ b/website/content/docs/concepts/integrated-storage/autopilot.mdx @@ -67,6 +67,14 @@ behavior. Autopilot gets initialized with the following default values. - `server_stabilization_time` - `10s` + +~> **Note**: Autopilot in Vault does similar things to what autopilot does in +[Consul](https://www.consul.io/). However, the configuration in these 2 systems +differ in terms of default values and thresholds; some additional parameters +might also show up in Vault in comparison to Consul as well. Autopilot in Vault +and Consul use different technical underpinnings requiring these differences, to +provide the autopilot functionality. + ## Automated Upgrades Automated Upgrades lets you automatically upgrade a cluster of Vault nodes to a new version as