Remove druid-operator tree from this repo in favor of apache/druid-operator repo#19156
Merged
gianm merged 2 commits intoapache:masterfrom Mar 15, 2026
Merged
Conversation
Essentially reverts apache#18435 since the repo has now been moved to https://github.com/apache/druid-operator as part of the ASF donation.
Member
|
should we add a thing somewhere, like maybe in top level readme, that points to the other repo? |
clintropolis
approved these changes
Mar 14, 2026
AdheipSingh
approved these changes
Mar 14, 2026
Contributor
AdheipSingh
left a comment
There was a problem hiding this comment.
Thanks @abhishekrb19 .
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
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.
Essentially reverts #18435 since the druid-operator code has now been moved to its own dedicated Apache repository https://github.com/apache/druid-operator. We're tracking the first release through this issue continuing discussion from here.