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.

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

Make more installation configurations available #47

Open
z9r5 opened this issue Feb 16, 2018 · 3 comments
Open

Make more installation configurations available #47

z9r5 opened this issue Feb 16, 2018 · 3 comments

Comments

@z9r5
Copy link
Contributor

z9r5 commented Feb 16, 2018

All clusters are different: bare metal, GCE, AWS, Azure… There should be several installation configurations:

  • ClickHouse with local index on each node. Best option for bare metal; it lowers network delays between fluentd and ClickHouse;
  • ClickHouse as a cluster. Best option for cloud based K8s (GCE, AWS, Azure);
  • Standalone ClickHouse. For small K8s clusters or testing purposes. ClickHouse is installed on single node while fluentd is placed on each node.
  • External ClickHouse. ClickHouse is installed outside the cluster and is used as an external service while fluentd and dashboard are installed in the cluster.
@diafour
Copy link
Contributor

diafour commented Sep 5, 2018

More feedback about installation:

  • helm should not be required

@trusch
Copy link

trusch commented Nov 27, 2018

👍 A helm-less install would be much appreciated.

@diafour
Copy link
Contributor

diafour commented Apr 14, 2020

  • clickhouse setups not managed by loghouse chart:
    • external clickhouse cluster addressed by a hostname (ExternalName?, ha proxy?)
    • internal clickhouse in its own namespace

related to #146

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants