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

Add Production-ready druid cluster spec #200

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

schmichri
Copy link
Contributor

@schmichri schmichri commented Jan 15, 2025

This shall help users to adapt to the setup and config of Druid on Kubernetes using your operator. Due to the current lack of examples I've posted this on the druid slack channel and @AdheipSingh thought it would be of value here.

Description

In Context of the fahrbar20 project from iunera for the German Ministry of Digital and Transport, we decided to publish all our code and findings. Furthermore we love Druid and want to help with the adaption of users.


This PR has:

  • been tested on a real K8S cluster to ensure creation of a brand new Druid cluster works.
  • been tested for backward compatibility on a real K*S cluster by applying the changes introduced here on an existing Druid cluster. If there are any backward incompatible changes then they have been noted in the PR description.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added documentation for new or modified features or behaviors.

Key changed/added files in this PR
  • docs/README.md

@AdheipSingh AdheipSingh merged commit 1430903 into datainfrahq:master Jan 15, 2025
1 check passed
TessaIO pushed a commit to TessaIO/druid-operator that referenced this pull request Jan 26, 2025
TessaIO pushed a commit to TessaIO/druid-operator that referenced this pull request Jan 26, 2025
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

Successfully merging this pull request may close these issues.

2 participants