[CSR-3204] feat: Replace elasticsearch with clickhouse in the EKS setup docs #38
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agoldis
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EKS deployment docs are updated to use clickhouse instead of elastic.
I've gone through and tested these steps in EKS
One item of note is that we just have a single node clickhouse server.
I did test both with replicas and with shards, (these were easy to setup with the choosen operator), but our application doesn't use ON CLUSTER statements for schema creation or ReplicatedMergeTree for engines, so I was unable to take advantage of a multinode cluster.
Leaving it as 1 node for now, and we can explore enabling sharding later when the need arises. (replicas likely not needed for our current use-cases)