Anyone here actively working on the druid-operator ( https://github.com/datainfrahq/druid-operator) ?

cc: @Razin Bouzar

@Lee Schumacher, we have completed the work in migrating the operator into the druid repo, so it's now under the Apache umbrella (reference). We have two issues that are related to releases, governance, and Helm chart distribution. (#18581, #18582) . I have a local change to work on 18581, but some open items remain on 18582.

Not to hate, but yesterday I kinda was shocked by only few settings are supported by the ={"type": "environment","variables":{"secret1": "SECRET1_VAR",}} version It only works on passwords, so I had a few crashes as well trying to set up until I did like docker and use an env like druid_metadata_storage_connector_connectURI and removed the configs I want to put this into the docs, I was going to update the PR to https://github.com/datainfrahq/druid-operator Does this means I can publish to both now

Maybe update just to the Apache Druid repo so we can minimize the reconciliation for when the operator is moved into its own repo.

when do you think the transition to the new repo will happen ? I'm actively working on a feature (see https://github.com/datainfrahq/druid-operator/issues/244).

also, where are these plans being discussed/announced? The datainfrahq fork has no status update, the 1.31 release was announced in their newsletter on Oct 9 (of 2025). When do you expect to have a release from the apache version?

The working group comprised @Adheip Singh, @Eyal Yurman, and myself worked on the donation. An issue was opened in the operator repo. There is call for maintainers thread in the Apache Druid dev email list. The working team is more than happy to collaborate and include anybody interested in participating.

oh - the druid-dev email list? I'll join that, thanks.

I'm going to send a note to the #druid-operators channel as well. Thanks for calling that out.

Please submit contributions to existing https://github.com/datainfrahq/druid-operator - since at current stage the apache repo druid operator isn't actually usable. Once we are done with a new repo and all the formalities i will port all the changes to the new repo. It will be easier for me to track all changes.

Hey Lee, the repo available and we are working to cut a first release, so PRs can be submitted here.