-
Notifications
You must be signed in to change notification settings - Fork 42
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
Configuration question for running Druid with the Operator #68
Comments
+1. I am attempting to evaluate Druid for a few use cases. We run nearly all of our infra on k8s. I have found this operator to be practically unusable because of lack of documentation. Pointing to the CR spec and straight to druid docs is not helpful. Having the only example support only a single node cluster is also not helpful since there is nothing to compare against. Please please please provide even basic docs and examples. |
@Jmoore1127 i totally understand your concern. We have basic documentation to get started. We also have a druid operator slack community to get started. There is a video session on druid on k8s which can help you get started. I personally have been constrained on time, we are building a documentation and tutorials to get started. |
When I'll have a production-grade Druid cluster up and running I will also add mine as an example |
Thanks all. I understand how large an undertaking good documentation and examples really is. It is much appreciated. |
Hi @Jmoore1127 If you've got any specific question/use-case you're missing please ping us in the druid-operator channel / add context to the issue I opened. |
@AdheipSingh in your video at 38:22, you mention that you are using Druid Operator to manage multiple Druid Clusters. Can you post your Druid CR Spec YAML for others to reference? |
From the druid-operator Slack channel:
The text was updated successfully, but these errors were encountered: