From 43e6c608d98b7e062f57ec953bc3a736619eccd1 Mon Sep 17 00:00:00 2001 From: Muhammad Faizan Date: Mon, 22 Apr 2024 16:06:53 +0200 Subject: [PATCH 1/3] chore: add information about high availability of NATS servers --- docs/user/02-configuration.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/user/02-configuration.md b/docs/user/02-configuration.md index c93f6a81..5522a5a3 100644 --- a/docs/user/02-configuration.md +++ b/docs/user/02-configuration.md @@ -25,6 +25,10 @@ Use the following sample CRs as guidance. Each can be applied immediately when y - [Minimal CR](https://github.com/kyma-project/nats-manager/blob/main/config/samples/minimal.yaml#L1) - [Full spec CR](https://github.com/kyma-project/nats-manager/blob/main/config/samples/nats-full-spec.yaml#L1) +## High availability + +NATS Servers are set up across different Availability Zones for uninterrupted operation and uptime. To achieve this, a minimum of three Kubernetes nodes must be distributed across at-least 3 Availability zones. Failure to meet this requirement will result in NATS Servers being scheduled within the same Availability zone, compromising high availability. + ## Reference From db328969f94edbd5b796e73a66c1efaafd976a36 Mon Sep 17 00:00:00 2001 From: Muhammad Faizan Date: Mon, 3 Jun 2024 10:56:02 +0200 Subject: [PATCH 2/3] updated --- docs/user/02-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/02-configuration.md b/docs/user/02-configuration.md index 5522a5a3..2445bc75 100644 --- a/docs/user/02-configuration.md +++ b/docs/user/02-configuration.md @@ -27,7 +27,7 @@ Use the following sample CRs as guidance. Each can be applied immediately when y ## High availability -NATS Servers are set up across different Availability Zones for uninterrupted operation and uptime. To achieve this, a minimum of three Kubernetes nodes must be distributed across at-least 3 Availability zones. Failure to meet this requirement will result in NATS Servers being scheduled within the same Availability zone, compromising high availability. +NATS Servers are set up across different availability zones for uninterrupted operation and uptime. To achieve this, a minimum of three Kubernetes Nodes must be distributed across at least three availability zones. If this requirement is not met, high availability is compromised because NATS Servers would then be scheduled within the same Availability zone. ## Reference From a66fab34b7cd999707997fbc5fe7a3f7ea662218 Mon Sep 17 00:00:00 2001 From: Muhammad Faizan Date: Mon, 3 Jun 2024 13:26:56 +0200 Subject: [PATCH 3/3] Update 02-configuration.md --- docs/user/02-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/02-configuration.md b/docs/user/02-configuration.md index 2445bc75..244c6cc8 100644 --- a/docs/user/02-configuration.md +++ b/docs/user/02-configuration.md @@ -27,7 +27,7 @@ Use the following sample CRs as guidance. Each can be applied immediately when y ## High availability -NATS Servers are set up across different availability zones for uninterrupted operation and uptime. To achieve this, a minimum of three Kubernetes Nodes must be distributed across at least three availability zones. If this requirement is not met, high availability is compromised because NATS Servers would then be scheduled within the same Availability zone. +For high availability, the NATS servers must be set up across different availability zones for uninterrupted operation and uptime. NATS Manager deploys the NATS servers in the availability zones where your Kubernetes cluster has Nodes. If the Kubernetes cluster has Nodes distributed across at least three availability zones, NATS Manager automatically distributes the NATS servers across these availability zones. If the Kubernetes cluster doesn’t have Nodes distributed across at least three availability zones, high availability is compromised. ## Reference