Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add information about high availability of NATS servers #365

Merged
merged 3 commits into from
Jun 3, 2024
Merged

chore: add information about high availability of NATS servers #365

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
43e6c60
chore: add information about high availability of NATS servers
mfaizanse Apr 22, 2024
db32896
updated
mfaizanse Jun 3, 2024
a66fab3
Update 02-configuration.md
mfaizanse Jun 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/user/02-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
mfaizanse marked this conversation as resolved.
Show resolved Hide resolved

## Reference

<!-- The table below was generated automatically -->
Expand Down