Skip to content

Commit 939edd7

Browse files
committed
Clarify setting and usage of CLOUD_PROVIDER
1 parent 1e026fb commit 939edd7

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

CHANGES.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ Unreleased
1414

1515
* Fixed JWT auth handlers for clusters without users.
1616

17+
* Clarify usage of ``CLOUD_PROVIDER`` in the documentation.
18+
1719
2.41.1 (2024-08-30)
1820
-------------------
1921

docs/source/configuration.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,13 @@ expected to use upper case letters and must be prefixed with
2323
in one availability zone (AZ) of that corresponding AWS region. If all
2424
copies of some shard were located in the same AZ, an outage of that AZ would
2525
imply some data being unavailable in CrateDB.
26+
This variable is optional. If it is set, make sure that the underlying
27+
Kubernetes Nodes are configured with availability zones.
28+
The operator will then use this information to ensure that CrateDB nodes are
29+
spread across different availability zones. This is done by setting the
30+
``node.attr.zone`` attribute on CrateDB nodes.
31+
The operator also sets annotations on the Kubernetes Loadbalancers, based on
32+
``CLOUD_PROVIDER``.
2633

2734
To ensure CrateDB properly replicates shards to other nodes in different
2835
availability zones, one can make use of CrateDB's :ref:`routing allocation

0 commit comments

Comments
 (0)