• Druid Operator provisions and manages Apache Druid cluster on kubernetes.
• Druid Operator is designed to provision and manage Apache Druid in distributed mode only.
• It is built in Golang using kubebuilder.
• Refer to Documentation for getting started.
• Feel free to join Kubernetes slack and join druid-operator

• Apache Druid on Kubernetes

• Druid Summit 2023
• Dok Community
• Druid Summit
• Druid Operator Blog
• Druid On K8s Without ZK
• Building Apache Druid on Kubernetes: How Dailymotion Serves Partner Data

• The operator supports CR's of type Druid and DruidIngestion.
• Druid and DruidIngestion CR belongs to api Group druid.apache.org and version v1alpha1

• The project moved to Kubebuilder v3 which requires a manual change in the operator.
• Users are encourage to use operator version 0.0.9+.
• The operator has moved from HPA apiVersion autoscaling/v2beta1 to autoscaling/v2 API users will need to update there HPA Specs according v2 api in order to work with the latest druid-operator release.
• druid-operator has moved Ingress apiVersion networking/v1beta1 to networking/v1. Users will need to update there Ingress Spec in the druid CR according networking/v1 syntax. In case users are using schema validated CRD, the CRD will also be needed to be updated.
• The v1.0.0 release for druid-operator is compatible with k8s version 1.25. HPA API is kept to version v2beta2.
• Release v1.2.2 had a bug for namespace scoped operator deployments, this is fixed in 1.2.3.

Apache®, Apache Druid, Druid® are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. This project, druid-operator, is not an Apache Software Foundation project.